I am getting multiple reports from users that they can't get GPS or location services in my app until they restart their phone, and then everything works no problem.
I only get a limited sample of android users complaints, from the set of users that use my apps but it seems shockingly similar to this issue:
https://code.google.com/p/android/issues/detail?id=39745
Google OTA updates rolled out to some additional carriers last week. Looking through my code changes over the last several months, I haven't changed any GPS/positioning stuff except in cases where I had to use the new google maps, but I can't tell if my particular user complaints are coming from a very old version or an upgrade from a very recent version or whatever version.
It appears to be related to Android 4.2 but I can't confirm that either, except the similarity of users restarting their phone and everything magically solves itself. I don't consider this a valid troubleshooting option though for my users.
Basically wondering if anyone else has solved this in code, and also putting it here in case other developers can relate to this
Related
i'm new to coding and as a final project on a course I decided to build and Android app, since it's what I want to focus my studies later (kinda regret it now...).
My idea is about an app that will have GPS services and actions based on GPS locations, so I started following tutorials from the basics up, now i'm following a basic tutorial about a GPS app (in Kotlin) that just displays the current location with an on/off switch.
I'm still getting familiar with Android Studio and all the methods etc, but as of now I got to solve many of my problem since the documentation is plenty.
For the last 4-5 days i'm struggling to get it to work since i never got to get the location from it, I've followed the tutorial, I've copied code from repositories that followed the same tutorial, but in the console I keep getting:
2022-07-13 15:06:25.275 4791-4815/com.example.gps_activity_test W/GooglePlayServicesUtil: com.example.gps_activity_test requires the Google Play Store, but it is missing.
2022-07-13 15:06:25.275 4791-4815/com.example.gps_activity_test W/GoogleApiManager: The service for com.google.android.gms.internal.location.zzaz is not available: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}
up until today the second error message was logging
android.gms.internal.service.zap
instead of
android.gms.internal.location.zzaz
I've been searching for service.zap, or googlePlayServiceUtil or GoogleApiManager, but nothing to help, and I only found this github issue for an errorcode similar to mine, but I haven't understood much anything about it.
I've reinstalled google play services in my emulator, and tested the app on my physical phone but no luck.
Also using custom logging messages or displaying a text update only goes so far in the code before this problem blocks it from proceeding
The app seems to work fine, it doesn't crash, but the UI values stay at 0.0 not updating with the location informations, since I guess the app doesn't receive.
All the videos i've watched only ask for COARSE_LOCATION and FINE_LOCATION while only adding implementing the 'com.google.android.gms:play-services-location:20.0.0' copied from the documentation and also added and removed others following what I understood from the docs
As a beginner, the android doc is kinda a nightmare to understand plus it seem to constantly change and reading questions/answers or tutorials from just a year ago, many methods or arguments are different or deprecated.
Any insights on what to do?
I've been stuck for 4-5 days with no step forward...
Going on with the tutorial seems useless, since it is all based on locations, so even if I copy all the new features and functions, I'd still be stuck not knowing if they're working or not.
thanks for your time, sorry if I didn't provide enough context
Reinstalled Android Studio
Reinstalled the emulated device (specifically choosing one that has already google play store installed) and opened the project again.
Now it works also on my physical phone.
This sparked a little argument in my office. I noticed that some of my colleagues see WhatsApps recently introduced "end-to-end encryption" message in their chats while some don't. Why is it that others can see that message and others can't? Is it because my whatapp version is more recent than theirs? What really happens when a mobile app gets updated to a recent version by it's developers, shouldn't everyone anywhere regardless of android get the same update at the same time? Or is this somewhat related to the android version which in turn is managed by and dependent on the hardware manufacturer?
I've got a development partner who says that in order to fix bugs that cause an application on iOS & Android to crash on load that end users need to delete the original app and re-download the new updated version. Are they for real? Shouldn't it just be incorporated into a standard app update and work like any other update?
The answer depends on how your app was distributed. If you just sent out a link like http://www.mysite.com/mytestApp.apk, it's easiest to uninstall. If they're updating via the Google Play Store, you have to set your version number higher than the installed version. Users can then get the newer version more seamlessly. I haven't done an ad hoc distribution with iOS yet, but updates via the app store seem to work similarly to the Play store. Users get a notification and can then update if their device meets the required specs.
Usually an update should resolve these issues. However, I have seen rare instances where users running older apps will need to uninstall/reinstall to get the new version of the application working. Like I said, these are rare instances where some major configuration has to take place. It's not something most updates need to do.
OK, this is a little obscure, and my first question on stackoverflow.. I have searched around for an answer to this, but couldn't find anything about this very specific issue. Here goes:
I have created a very simple app which will run as a service in the background, every once in a while it will add latitude & longitude entries to an sqlite database table. It uses course location information (without checking whether it is available).
I have installed the app (from an apk) on my device and never had issues with it. However, I installed it on my mother's droid and kept getting "unexpectedly quit" errors each time I ran it. Realizing that she may not have had cell-tower based location enabled and that my app was not designed with best practices in mind (to have checked for that), I quickly enabled that option in her device settings and re-ran the app. I still got a force quit..so I rebooted.. re-ran.. no dice.
Then, on a weird hunch, I decided to install the app again, but this time the course-location was enabled at install time. To my surprise, the app worked flawlessly after that.
So.. I've not confirmed any of these "theories" but thought the great community at stackoverflow would be my best bet for some ideas:
Somehow, it matters at install time that my app has course-network
enabled..although, that would seem to be a glaring bug and not
likely (because so many apps would have this problem otherwise)
unless somehow installing from market and installing from an apk
will yield different results.
Somehow, my app, written with bad practices, corrupted something in
its installed location and was wiped upon reinstall...
If someone could shed light on this, by sharing some of what they know about these two ideas (or maybe point out an entirely different idea that would explain this behavior) that would be awesome.
ACCESS_COARSE_LOCATION is a must to be able to access to wi-fi aided location info. ACCESS_FINE_LOCATION only gives you GPS location data. If you enable both permissions, you can switch between these two sources.
I have an app (All operators' APN | Tweakker) and it's been on the market for a while now. I discovered this week that I can't find it from my device's market anymore although I used to be able to. Nothing in the app has changed. If I go to the web market I get a message that confirms the app is compatible with my Desire. I tried finding the app with other phones as well, even from different countries, and it just doesn't appear.
Here's what I tried so far:
unpublish, publish
change promotion preferences
release a small bugfix update
wait for the Market to return to normal
Someone suggested the single quote might be a problem, but that can't be the case since this worked up to this week. The app is using copy protection.
The app seems to appear in the market now, although I haven't done anything more. I did contact Google, but I don't have an answer from them yet.