Ive try to send basic Android Build as tutorial says but Im getting this error. PS: I never would made any build before, and every day this message persists. (I`m using the Free account).
build-for-android-device:
[codeNameOne] You have a build in progress within the queue. Only one build may be active at a time
Someone may help me?
Looking at our support logs I think this was an issue that was resolved by a support engineer. The issue was related to an email account containing a + sign in the address specifically name+name#domain.com
Since our system uses emails to identify users this caused some issues and failed to show builds that went thru. So there was a build stuck in queue that never got built...
Restart your IDE, operation system.
You have queue of build right now.
Related
Just recently my GAE app stopped working and it cannot connect to cloud storage and a couple of more issues. I am using GAE and Spring Boot Rest Api.
When I deploy the app on the same version multiple times, one of them randomly works. It is just crazy.
Anytime it does not work, I get different errors like:
java.lang.NoClassDefFoundError: io/jsonwebtoken/io/SerializationException
Sometime I get another error:
NoSuchMethodError: com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;J)V
If I deploy the app multiple times using IntelliJ, magically, I do not get any error for one of the deployments. Is something going on with GAE deployment?
I have used the latest version of BOM to prevent any conflicts in my Maven libraries, and still no luck. It just happened out of blue last week without even changing the code. The version that I had online, stopped working today and I had to deploy the app multiple times until one of them worked.
The app works perfectly on my local machine.
Anyone who encounters this issue. You need to update your appengine-api-1.0-sdk and google-cloud-storage to its latest version. I used Maven to update and fix the issues.
I also got multiple errors because of using io.jsonwebtoken. The error was:
io.jsonwebtoken.security.weakkeyexception: The verification key's size is 48 bits which is not secure enough for the HS256 algorithm
I changed my JWT to auth0 library, and now it works.
Guess why all these things happened? Because Google updated some of the structure of their GAE and if you do not update your app engine you will get an unlimited number of errors with a perpetual cycle of debugging. I hope Google updates people when they make such huge changes that affect many websites.
Admittedly, I have very minimal programming experience and this is my first time using Android Studio so bear with me. I am looking to determine what's causing my Samsung J3 Prime to crash and Firebase Crashlytics seemed like a good route to take.
I've been following the guide found here and am on Step 3, adhering to the 'Kotlin+KTX' instructions (that's just what I happened to choose for the project), but when attempting to sync the build I'm getting error
Failed to resolve: com.google.firebase:firebase-crashlytics.ktx: Affected Modules: app
yet when I remove the .ktx suffix as per the Java instructions it syncs successfully -- why is that? Am I missing or misreading something?
Any help or guidance is appreciated -- thanks!
We are seeing this very generic error pop up in some circumstances, but we can't seem to track down what is generating it and I'm hoping someone has some insight into where to begin. We have multiple client machines all running the same version of our software, build with SWT, and all hitting the same server, but not everyone gets this error. Nothing is showing up in our client or server logs and I have no idea what log file this error may be referring to, so it's not an error that we are catching anywhere and we have no details about this. Since it's a pop-up message that leads me to think it may be an SWT error. I've seen people mention this error when using Eclipse, but I haven't found where anyone mentioned it in an application they built.
I know this is vague, but I don't have much more to go on. Does anyone have an idea where to start looking for culprits?
Thanks
You're building an RCP application? In that case, this error is talking about the Eclipse platform log.
There should be a .metadata\.log file in your program's instance location. If you do not know your instance location, you can query it by calling:
Platform.getInstanceLocation();
I've been wanting to try using AppEngine in conjuction with my android app. My main problem is i can't seem to get the installation to work corrently, or at least that's what i'm assuming is going wrong.
I installed appengine and all the required plugins with eclipse from the instructions here http://code.google.com/eclipse/docs/appeng_android_install_setup.html But even when i just try run the test project it crashes without error (or at least nothing shows on LogCat or console) when i try and get it to send a message to the webserver and crashes about a minute after just adding a google account on the emulator. Is there any way to fix this that anyone knows of? Or perhaps another tutorial to install, it's getting to the point i'm not really sure where to go from here.
I have a Java app deployed on app engine and I use appcfg.py of the
Python SDK to vacuum and update my indexes.
Yesterday I first ran vacuum_indexes and that completed successfully -
i.e. it en-queued tasks to delete my existing indexes.
The next step was probably a mistake on my part - I then ran
update_indexes even though my previous indexes weren't yet deleted.
Needless to say that my update_indexes call errored out. So much so
that now when I look at my app engine console, it shows the status of
all my indexes as "Error".
A day has passed an it still shows the status on my indexes as "Error".
Can someone help my out of my fix?!
Thanks,
Keyur
P.S.: I have posted this on the GAE forums as well but hoping SO users have faced and resolved this issue as well.
I followed what was suggested in the error logs and that worked for me:
Empty the index.yaml file (create a backup first)
Run vacuum_indexes again
Look at your app's admin console and don't go to the next step till all your indexes are deleted.
Specify the indexes you want to be created in index.yaml
Run update_indexes
Look at your app's admin console and it should show that your indexes are now building.
Enjoy the fruits of your labor :)
Cheers,
Keyur