Something went wrong with the plugin api что делать
Can not install Slider plugin
I am trying to install plugins and both Revolution Slider and LayerSlider installation fail with same error:
“Something went wrong with the plugin API”
I read somewhere that deleting of existing plugins directories can fix it, but in my case, there are no relevant directories.
Avada version 5.5.2
WP version: 4.9.6
Any ideas?
Other plugins installed normally
There is currently a problem with one of the datacenters which our server uses. This should be a temporary issue and should be resolved soon.
Sorry for the inconvenience.
This should now be fully restored and working.
For me it’s still not working, I get this message:
Service Unavailable
Plugin not activated. A higher version of LayerSlider WP is needed for this theme. Please update the plugin.
I’m working with
Avada version 5.5.2, WP version: 4.9.6 and trying to install Revolution slider v5.4.8
It’s the same error I got yesterday. Then the error became “Something went wrong with the plugin API”
That is a different error. It will mean there are permissions issues in removing the older folder to add the new folder. If you go to wp-content/plugins you should see that there is still an old folder for Layer Slider. Delete the old one and then click to install new again. That should then work.
Alternatively you can go to Support > My Account – Avada Plugins on this website and download the Layer Slider plugin from there.
On further checking that may also be related to the same server issue. I will check into it some more and let you know when there is more information.
If you require the download you should still be able to access this from the my account page. Alternatively on the screen where your plugin update fails, if you copy the download URL to the address bar you should be able to download from there too.
where can I get the link to install a fresh Revolution Slider and what are the files that I need to remove?
Hi, I already mentioned above where the file can be downloaded from. The Avada Plugins tab on here https://theme-fusion.com/support/account/
The folder name for Slider Revolution is wp-content/plugins/revslider.
Hi, i have the same problem and in “my account” the download of this plugin is wrong too “A temporary error has occurred. If the problem persists, please visit my.wpengine.com or check our status blog for updates.”
You have have valid Grandfathered support and because our team does not provide support via the Community forum, please create a ticket using the link below and our team will gladly assist and check your install.
We look forward to helping you!
I am having the same issue. Fresh install of Avada and WordPress. All other plugins install but Revolution Slider and LayerSlider error out with: Download failed. Service Unavailable
Is there still server issues?
If you read the above, the plugin can be installed manually via FTP if so required (instructions above) or create a support ticket so that our team can assist you if you are stuck.
We look forward to helping you!
I was able to install manually. Would be nice if the automated install was properly fixed.
Thanks for your help.
I sent a support ticket because from the “my account” page, as I said, the downloads do not work and can not be installed manually
AAPT: error: resource android:attr/lStar not found #440
Comments
swadeshkamlesh commented Sep 30, 2021 •
Execution failed for task ‘:app:processDebugResources’.
FAILED
Android resource linking failed
C:\Users\kamlesh.gradle\caches\transforms-1\files-1.1\appcompat-1.4.0-beta01.aar\97b333eeae39b4b443d1c2079f33a72e\res\values\values.xml:2422:5-2449:25: AAPT: error: resource android:attr/lStar not found.
error: failed linking references.
BUILD FAILED in 34s
23 actionable tasks: 21 executed, 2 up-to-date
D:\ionic\carworld\platforms\android\gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.
Android resource linking failed
C:\Users\kamlesh.gradle\caches\transforms-1\files-1.1\appcompat-1.4.0-beta01.aar\97b333eeae39b4b443d1c2079f33a72e\res\values\values.xml:2422:5-2449:25: AAPT: error: resource android:attr/lStar not found.
error: failed linking references.
BUILD FAILED in 34s
Bug report
CHECKLIST
I confirm this is a suspected bug or issue that will affect other users
Current behavior:
Expected behavior:
Steps to reproduce:
Screenshots
Environment information
Android build issue:
Related code:
Console output
Other information:
The text was updated successfully, but these errors were encountered:
AndroidJavaException: java.lang.NoSuchMethodError #3002
Comments
sgeorge1970 commented Feb 10, 2021
When calling PlayGamesPlatform.Instance.LoadScores
I am getting this error:
AndroidJavaException: java.lang.NoSuchMethodError: no non-static method with name=’getStatusCode’ signature='()I’ in class Ljava.lang.Object;
I’m using 0.10.12 GPS unity package
this does not occur if I go to 0.9.64 GPS unity package
Any guidance would be great!
Steve
The text was updated successfully, but these errors were encountered:
ososmam commented Feb 16, 2021 •
Same with PlayGamesPlatform.Instance.SavedGame.OpenWithAutomaticConflictResolution using 0.10.12
Quawetim commented Mar 1, 2021
Same with PlayGamesPlatform.Instance.SavedGame.OpenWithAutomaticConflictResolution using 0.10.12
hbaInfinity commented Apr 12, 2021
I can confirm the exact same message as the above people using 0.10.12. This was not happening in previous versions. This is also failing on the PlayGamesPlatform.Instance.SavedGame.OpenWithAutomaticConflictResolution call above.
The weird thing is that it is only happening on some devices. I am currently testing on a Samsung A30 on Android 10 (security patch 1st March 2021) where it all works perfectly, but another phone using the exact same Google Play log in, which is the Oppo AX5s on Android 8.1.0 (security patch 5th Feburary 2021) is failing with the issue above.
MoodyMuffin commented Apr 13, 2021
When calling PlayGamesPlatform.Instance.LoadScores
I am getting this error:
AndroidJavaException: java.lang.NoSuchMethodError: no non-static method with name=’getStatusCode’ signature='()I’ in class Ljava.lang.Object;
I’m using 0.10.12 GPS unity package
this does not occur if I go to 0.9.64 GPS unity package
Any guidance would be great!
Steve
mgrogin commented Apr 14, 2021
hbaInfinity commented Apr 15, 2021
Just as something else I have seen with this issue, it seems like it is affecting logging into the Google Play Games account on the device that it affects. Here is the current flow of what I am observing:
This is happening on the Oppo AX5s on Google Play Services plugin 0.10.12, but everything works fine on a Samsung A30.
As a side note, these same devices work with this plugin on one of our other games, with the exact same code, but running on 0.10.04.
Any help on how to fix this is appreciated, as it is breaking almost all of our Google interactions on these devices.
MoodyMuffin commented Apr 16, 2021 •
I made a quick temporary fix, not beautiful, but it worked for me. Here is the idea:
In my case error happens inside AndroidSavedGameClient.cs in method ‘AddOnFailureListenerWithSignOut’
We add ‘AddOnFailureListener’ and try to call ‘getStatusCode’ from Exception object. But ‘getStatusCode’ is method for ApiException, which inherited from Exception. Exception doesn’t have this method. I think this is the problem. So I cast Exception to ApiException if it possible, and after that trying to call getStatusCode. I do it in java class and call it from Unity.
import com.google.android.gms.common.api.ApiException; import com.google.android.gms.common.api.CommonStatusCodes; @UnityCallable public class ExceptionsUtils < @UnityCallable public static int GetStatusCode(Exception ex) < if (ex instanceof ApiException) < return ((ApiException) ex).getStatusCode(); >return CommonStatusCodes.ERROR; > >
Also I replaced the same way other cases of using ‘getStatusCode’ for Exception object
hbaInfinity commented Apr 19, 2021 •
Any pointers on this would be appreciated!
MoodyMuffin commented Apr 19, 2021
Any pointers on this would be appreciated!
Hey
In java file I define package name, like: ‘package com.A.B.C.D;’
java file is located inside app/src/main/java/com/A/B/C/D
And in C# file I call new AndroidJavaClass(«com.A.B.C.D.ExceptionsUtils»)
Also, this package is added in proguard-unity.txt, maybe you should try it too
hbaInfinity commented Apr 19, 2021
Thanks, After double checking, the java file does indeed get exported to the app/src/main/java/com/. directory when I build a gradle project, and I have defined the package name to be the same in the Java script and the C# script. The only main difference I have between the code is the that I let Unity generate the proguard-unity.txt, and that I am unable to get @UnityCallable compiling as it «Cannot Find Symbol». From what I have read up, it seems like just an interface in the Facebook plugin, but it doesn’t seem like it does too much, and other examples I have seen do not require it.
I do hate Unity’s lack of documentation on this stuff though, which would make things much easier than just a few dot points.
jonathanlindvall commented Apr 22, 2021 •
We just ran into the exact same issue after adding a 2nd OAuth credential (to be able to test Games Services when building locally with the Debug certificate). In our case, it seems like the problem was related to Saved Games. Turns out we had a cloud save that had been uploaded from an Internal Test version of the app, signed with Play App Signing. The app signed with the Debug certificate was not able to download this cloud save and crashed with the NoSuchMethodError (getStatusCode).
We were able to solve it by deleting the Play Games data for the game through the Play Games app ( Settings > Delete Play Games account & data ). Not sure if this is the same issue that you guys are having, but it might be worth a try if you’re using multiple OAuth credentials.
mgrogin commented Apr 22, 2021 •
I’m still looking for a perfect solution but figure this will help the community find the actual problem.
based on what @MoodyMuffin said I use this c# code that has an extension function that casts the AndroidJavaObject to com.google.android.gms.common.api.ApiException without having to use a java plugin.
So far I see that the object has been of 3 types:
«com.google.android.gms.common.api.ApiException»,
«com.google.games.bridge.TokenResult»,
«java.lang.IllegalStateException» // doesnt have getStatusCode function
By doing this I was able to see this error:
I/Unity: LoadScores failed: java.lang.IllegalStateException: Max results must be between 1 and 30
I think the bug might be related to this somehow.
Waiting to hear if anyone has any improvements or better solutions
heres the code:
mgrogin commented Apr 22, 2021
There’s still a bug with public void LoadScores(ILeaderboard board, Action callback) in PlayGamesPlatform.cs
Still getting the error though..
leandersonralves commented May 19, 2021
Hi folks, until some seconds ago, I was fighting against this issue.
But, I found a problem in my code.
I was building a Metadata with a PNG cover data with a Array Lenght equals zero.
I just remove this wrong line and solved. tadãh!
I suposse that I must pass a array with length zero in case without a png cover.
mgrogin commented Jun 24, 2021
mgrogin commented Jun 24, 2021
@aerialninja I see you made some changes to the github
What do you think about this change? #3002 (comment)
What do we need to do to get it in the next build and to make sure it’s correct? what’s the procces?
thanks in advance!
Plugin with id ‘maven’ not found. #12774
Comments
mantu-designersx commented Apr 29, 2021 •
Summary
I Just upgraded react-native from 0.62.0 to 0.63.0 and all was working fine. But after I integrated expo unimodules in my bare expo project when I try to make the build for android then expo dependencies give me the below error.
Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!
What platform(s) does this occur on?
SDK Version (managed workflow only)
Environment
React-native : 0.63.0
Expo Unimodules : 0.13.3
Gradle version : 7.0
Project : Typescript
buildToolsVersion = «30.0.0»
minSdkVersion = 21
compileSdkVersion = 30
targetSdkVersion = 30
Reproducible demo or steps to reproduce from a blank project
Error
The text was updated successfully, but these errors were encountered:
byCedric commented Apr 29, 2021
gilons commented May 3, 2021
me too I’m currently stuck with the same issue.
I’m on Mac book pro 2020 Catalina 10
node 16
gradle 7
any help will be highly appreciated
brentvatne commented May 3, 2021
@gilons, the same comment that @byCedric shared above also applies to you 🙂
Hi @mantu-designersx! Could you provide a reproducible example with this error? It seems like this is unrelated to unimodules, but more related to incorrect gradle version or missing gradle system features. If you can’t provide a repro, it might be useful to compare the gradle differences with a new project using npx create-react-native-app.
gilons commented May 3, 2021
Ok thanks
Let me see what to do.
gilons commented May 3, 2021
Hi @brentvatne thanks for your suggestion. à
The problem actually was with the Gradle version. I just had to downgrade my Gradle version to version 6.4.1 using sdk-manager while following this guide
then, gradle wrapper command worked
officialkirill commented May 4, 2021
I stumbled here via google search and just wanted to let you guys know that the ‘maven’ plugin was deprecated in gradle 7. The suggested replacement is maven-publish. I belive the previous plugin had a bit different purpose. I could be wrong, though.
jailsonpaca commented May 8, 2021
RupamShaw commented May 12, 2021 •
android studio 4.2 with gradle 7.0.1 gives below error
seanconrad1 commented May 20, 2021
@gilons this worked for me ty
gilons commented May 20, 2021
EwaTrzemzalska commented May 25, 2021
brentvatne commented May 25, 2021
android studio 4.2 with gradle 7.0.1 gives below error
this is a good solution. locking thread for now because we don’t support gradle 7.
djeanaraujo commented Jun 22, 2021
For those using gradle 7, maven plugin has been removed, now you should use maven-publish, as described in official site at this link: https://docs.gradle.org/7.0/userguide/upgrading_version_6.html?_ga=2.21245883.1883799052.1624281891-1948725710.1624281891#removal_of_the_legacy_maven_plugin
So, instead of using:
apply plugin: ‘maven’
you should use
apply plugin: ‘maven-publish’
gauravgg commented Jul 2, 2021
Hi @brentvatne thanks for your suggestion. à
The problem actually was with the Gradle version. I just had to downgrade my Gradle version to version 6.4.1 using sdk-manager while following this guide
then, gradle wrapper command worked
After installing gradle6.4.1 using sdk manager and setting gradle wrapper
I have used your method. I have used sdk manager and downgrade my gradle to 6.4.1 but my android studio artic fox supports only gradle 7.0 and my react-native modules do not support gradle 7.0. I am using macbook pro m1 chip. The error which i am getting is this:
Minimum supported Gradle version is 7.0.2. Current version is 6.4.1.
Please help me out on the same.
pjeremymalouf commented Jul 31, 2021
Hi @brentvatne thanks for your suggestion. à
The problem actually was with the Gradle version. I just had to downgrade my Gradle version to version 6.4.1 using sdk-manager while following this guide
then, gradle wrapper command worked
After installing gradle6.4.1 using sdk manager and setting gradle wrapper
I have used your method. I have used sdk manager and downgrade my gradle to 6.4.1 but my android studio artic fox supports only gradle 7.0 and my react-native modules do not support gradle 7.0. I am using macbook pro m1 chip. The error which i am getting is this:
Minimum supported Gradle version is 7.0.2. Current version is 6.4.1.
Please help me out on the same.
In the build.gradle file I changed this line:
classpath ‘com.android.tools.build:gradle:7.0.0’ to classpath ‘com.android.tools.build:gradle:4.2.2’
And it started working!
BenGroot commented Aug 19, 2021
Android Studio Artic Fox is promoting to upgrade to Gradle 7+. Almost everyone who is using the bare workflow with the latest Android Studio will get this issue. Mirgating to «maven-publish» will save a lot of hassle for developers who haven’t had this issue yet. Is this migration very complex?
BenGroot commented Aug 19, 2021
To summarise for those running into this issue:
Change gradle build tools in the main build.gralde to:
classpath ‘com.android.tools.build:gradle:4.2.2’
Change distribution url in the yourproject/gradle/wrapper/gradle-wrapper.properties file to:
distributionUrl=https\://services.gradle.org/distributions/gradle-6.8-all.zip
The jump between the 7.0 version and the versions mentioned above is so huge because they are aligning the version numbers with the Gradle version number. The versions mentioned above just before the 7.0 versions.
raybotha commented Aug 20, 2021
What’s the plan for supporting Gradle 7? Now that React Native supports it.
robertying commented Aug 22, 2021
For any expo package, go to its android/build.gradle and modify to use maven-publish plugin:
Guilhemfuel commented Aug 30, 2021
android studio 4.2 with gradle 7.0.1 gives below error
If I try to do this I get error : Unsupported class file major version 60
lejager commented Sep 3, 2021
To summarise for those running into this issue:
Change gradle build tools in the main build.gralde to:
classpath ‘com.android.tools.build:gradle:4.2.2’
Change distribution url in the yourproject/gradle/wrapper/gradle-wrapper.properties file to:
distributionUrl=https\://services.gradle.org/distributions/gradle-6.8-all.zip
The jump between the 7.0 version and the versions mentioned above is so huge because they are aligning the version numbers with the Gradle version number. The versions mentioned above just before the 7.0 versions.
This results in a number of No signature of method errors for certain react native packages.
No signature of method: build_1pnz21phoowefc22xejnoeuib.android() is applicable for argument types: (build_1pnz21phoowefc22xejnoeuib$_run_closure1) values: [build_1pnz21phoowefc22xejnoeuib$_run_closure1@23db40cd]
Anyone facing this?
+1 for gradle 7 support
bombillazo commented Sep 28, 2021
For any expo package, go to its android/build.gradle and modify to use maven-publish plugin:
This in conjunction with patch-package solved it for me! Also be aware you may have to update this inside unimodule dependencies too.
tisdadd commented Oct 13, 2021
For anyone who wants this temporary fix (please read the code yourself), I made a quick fix file with the examples here and from the replace-in-files node module. I realize that it is sloppy, but it should get everything for an upgrade. I had missed the publications part in my initial run, so I haven’t tested it with that.
nibblesnbits commented Nov 4, 2021
Is there any movement on this?
enigmablue commented Nov 20, 2021
unable to upgrade to gradle 7 too, which is required but some other packages. 🙁
brentvatne commented Nov 22, 2021
here’s a related issue about gradle 7: facebook/react-native#29829
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
[Known Issue] iOSResolver.dll failed to load with Unity 2021.1.11+ on Mac #441
Comments
chkuang-g commented Jun 22, 2021 •
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Please answer the following, if applicable:
What’s the issue repro rate? 100%, even with empty project.
Issue Statement
iOS Resolver library cannot be loaded in Unity 2021.1.11 and 2021.1.12. (Did not test 2021.2.0 beta yet). It can be loaded properly with Unity 2021.1.10.
After importing EDM4U, Unity logs an error like:
And iOS Resolver is not loaded, verified through the absence of Assets > External Dependency Manager > iOS Resolver menu item. The odd thing is that all the other libraries, ex. Android Resolver, Version Handler, are loaded with no issue.
The same issue has been reported on Unity forum here
This seems to be a regression introduced in Unity 2021.1.11 as documented in the release note.
Workaround
Since the issue is the mismatched library name, a simple workaround is to rename the dll file.
After the renaming, Unity should be able to load iOS Resolver library properly.
However, there is a caveat: After renaming, Version Handler will no longer able to manage those files. That is, when a newer version of EDM4U is installed, Version Handler will not be able to automatically remove the older version of iOS Resolver.
The workaround is to remove the entire folder of Assets/ExternalDependencyManager/ folder before upgrading.
The text was updated successfully, but these errors were encountered:
chkuang-g commented Jun 22, 2021
May need to explore other potential workaround.
chkuang-g commented Jun 22, 2021
Update: The issue does NOT occur with Unity 2021.2.0b1
patm1987 commented Jun 23, 2021
I am seeing this on Windows with 2021.2.0b1 (installed via Unity Hub) with EDM4U (v1.2.162 installed via the play games plugin).
The suggested workaround does work for me.
I am using Windows 10 (21H1) and my project is on an exFAT file system rather than NTFS.
Goncharuk-Nikita commented Jun 24, 2021
+1 also has this issue.
but 2021.2.0b1 does not work for me with Firebase and Facebook SDK.
I downgrade to 2021.1.10.
Barokoli commented Jun 30, 2021
+1 also had this issue on 2021.2.0b1
Mac Book M1
Workaround fixed it
joaquingrech commented Jun 30, 2021
I´ve just downloaded 166 hoping this was fixed. still same issue
Assembly ‘Assets/ExternalDependencyManager/Editor/Google.IOSResolver_v1.2.166.dll’ will not be loaded due to errors:
Assembly name ‘Google.IOSResolver’ does not match file name ‘Google.IOSResolver_v1.2.166’
gamefish commented Jul 2, 2021
+1 also has this issue.
waiting for the fix.
do not want to try workaround yet because we are develop under android, will be a few month later to release on iOS
chkuang-g commented Jul 7, 2021
itsarjunsinh commented Jul 20, 2021
@chkuang-g Could adding a version code variable inside the dll be a solution? It’s a shot in the dark, but I suppose you can then adhere to new naming conventions and still allow the version handler to manage files.
A fix for this would be great. Renaming files is particularly tedious for me since I use tarballs for dependencies. I’ve added a duplicate EDM via Unity package for now.
LaCreArthur commented Jul 26, 2021
Renaming the file manually did the trick, thanks, but it should not be that way
Thaina commented Sep 7, 2021
Are there any progress on this? What is the actual solution that will came out in future release? Is it the problem of unity itself or this google repo?
It seem this problem would affect firebase and facebook (and any other library depend on EDM4U) as well. And so we can’t update to 2021.2b
chkuang-g commented Sep 9, 2021 •
Why versions in filename?
Version information is not only stored in the filename but also in the Asset label and in code
Without the postfix, you will end-up having EDM4U 1.2.135 in your project since the same file name imported later override the existing one in the project. With the postfix, after you import Facebook SDK, EDM4U can kick-in and remove EDM4U 1.2.135 without you doing anything.