After making a Firebase app and implementing everything I needed, including the .json, gradle, etc. It all compiles fine.
The first time, it said either move to minSdk 23 or use multidex, I chose minSdk 23 for I don't know if that was it. But I am getting app not installed, even though there is no package interference.
It is being built and installed from the mobile IDE "AIDE". If you need any of my code or clarification, please ask. As I haven't had this type of error and I'm assuming I may be missing something. Thank You.
My problem ended up being I accidentally changed the action and category of .MainActivity so it wasn't "MAIN" and "LAUNCHER". Sadly, I did not end up getting the app itself working :(
Related
I am developing on React Native and using react-native-geolocation-service library to access foreground location only (App is for office and other location checkin purposes)
I recently faced this issue, last week I was still able to upload and release my aab just fine, but this week I can't anymore although I only changed a few UI based on user's feedback.
So basically permission and logic wise there's no change to my app.
I even compared both app's permission list and both are exactly the same:
But then I'm getting this error
even though I have specifically declared here that I'm not accessing background location
This app targetSdkVersion is 28, if that's important, because I heard starting API 28 there are alot of new restrictions on play console.
Have anyone ever encountered this issue?
If this is a problem with the library I'm using could anyone give me any pointers?
Thanks
Okay got it,
I looked into it and found this
https://developer.android.com/training/location/permissions#foreground
so I just added service tag like so
<service
android:name=".ForegroundLocation"
android:foregroundServiceType="location">
</service>
and updated targetSdkVersion to 29 and it worked!
Although still not sure which causes it to work lol
Can anyone explain this to me? Thanks!
I am programming in Android using LocationManager. I build a simple app that just shows the current location. And I got the error of the title.
Now, this question has been posted several times but before someone tags this question as a duplicate, please acknowledge that it is not, and I will explain why
All other questions explain that this problems is because Android 6 now require to explicitly ask for permission at runtime. So I did that and I solved my problem. (well it is almost working)
Why did I take so much time in solving it? It is because I had another version of the program that run without problems without any explicit request for permissions
This other version was yes, built before Android 23 I think, it was built in eclipse and I just downloaded the project, and imported it to Android Studio changing the platform in build.gradle to make it run successfully. So I thought that it was converted to Android 6 already.
So the imported program worked without any explicit request for permission but my program had to have this. Why is this so?
My second question is, the editor did clearly underlined in red the LocationManager functions declaring that they need explicit request for permission. (In the other imported program this did not happen) However even after I did ask for permission, and even after the program run successfully, it still underlined them in red. Why?
It seems strange, but I have several users who don't experience any trouble, and two others who do.
I can't see any difference but one : the version. The two users with the "not working" app are using Android 4.4.3.
All the others are using older versions.
The problem seems to be with the function ".isChecked()" on a radioButton (in a radioGroup).
It keeps sending "false" even if it is true.
I am absolutely sure it is the same version (I sent my app by the same email to all the users).
I do not understand this problem, it seems strange in this way. The function "isChecked" exists since the first API ! (according to the official developer website)
If anyone has an idea...
Thanks !
it seems you are using a android:targetSdkVersion that is below the two user where the app is not working .
try to change this code in you AndroidManifest.xml
<uses-sdk
android:minSdkVersion="minimun target android version "
android:targetSdkVersion="it should be < = to your friend's android version " />
I have an application that uses a native library (.so).
In the new version of the application I made changes in the lib. The problem is that after upgrading the application it looks like the new library is not loaded.
If I force stop the application and then I restarted it everything works fine.
In some cases just waiting for a while (for example 20 mins) fixes the problem.
Did anyone experience this issue?
Is there a way to fix it?
EDIT
I have also tried to call
System.loadLibrary("mylib.so");
in the onReceive of the OnUpgradeReceiver that is the broadcast receiver that is registered to be called when the application is upgraded
It did not help
EDIT2
I think this issue has to do with the fact that the lib uses the audio engine. The reason iwhy I think so is that I tried to change the name of the lib and it did not help either
Ok never mind I think the issue is just in my lib. I need to find where but I checked that the application is properly closed after the upgrading.
I have submitted an app to the Amazon app store. It has been rejected twice now for the same reason, but I can't find the problem. It crashes right at the start, usually 2-3 activity windows in. This error never happens on our test devices, and there hasn't been a single error or crash from the app on the Google market. So thus far I've been completely unable to replicate the error.
On the last rejection we requested a stacktrace, which they sent, but only with errors, not warnings, which from what I gather is what I need to find out exactly what method is causing the Java.Lang.VerifyError from W/dalvikvm. Is it reasonable to assume that when they decompile the app, and inject their amazon drm/tracking/whatever code into the app, and recompile it, it's causing clashing errors with some of my code? or that Amazon are possibly compiling on a different version of Java than we are? (ours is 1.6)
The app has both minSDK and targetSDK set to api8, which is 2.2 minimum, and we compile it against 2.2, Has anyone else had this error with Amazon before and might be able to give me some insight as to how the problem was resolved?
Thanks
Found the problem. In the Manifest there was a .java file that was declared as an activity, which it was originally, but it had been changed to extend Dialog instead.
When Amazon injects code into your app, they look at the manifest to find the Android Activities, and inject code into them such as callbacks and method overrides, some of which are specific to the Activity class. When Amazon looked at my manifest, they thought the class was an Activity, but it was actually now a Dialog, and the app was crashing when trying to override methods that didn't exist.
Once removing the manifest declarations to the classes that weren't actual Activities, the app got approved. Its weird that google and eclipse didn't pick up on the declared activities that weren't activities when the app got compiled.
Hope this can help others who cant seem to find out the reason their apps not getting approved by Amazon.