I have a problem with my Google Play Cloud api. I tried to find some sort of support and was lead to Stack Overflow. I am using the "google play game service" for my Unity-based game (to store the save-game via Cloud).
Since my newest releases I had a small issue with the GPGS-implementation, which I fixed immediately. Every error disappeared after my fix. But since the patch last month, one error still remains with 100% appearance:
"google.play.games.games.v1.Applications.RecordApplicationActivity"
I can't find anything online about similar issues or nearly the source of this call, to fix this on my own.
I can't reach that bug via testings on my test-devices, nor does it seem to affect my users dramatically, but an error is nothing I should ignore...
What things can I do to investigate this?
This is the most detailed Error-Help I can get
Always check your SHA1 key!
I assumed the guide next to the SHA1-Input to get the SHA1-Key was the right one for me. Apparently there are 2 SHA1 Keys (one "SHA1-App-Key" and one "SHA1-Upload-Key")... And you don't even need that "cmd-guide" from google. If you already uploaded your app, you can find BOTH keys in the google console. Under "Release" & "App-Integration".
The problem I'm facing is that for a given custom event, sometimes certain event parameters are missing in Firebase, even though logcat is showing that everything was submitted correctly. Most notably, sometimes even some of the firebase_* and ga_* parameters are missing in the DebugView. No errors are showing up in logcat or anywhere else.
The set up is as follows:
Blaze plan
6 custom event parameters in total
firebase-analytics:17.2.0
Android API 28
Not reproducible on iOS, only on Android
Unfortunately I can't provide a MCVE right now, but maybe someone has ideas what could potentially cause this? Is this a bug in the Firebase Analytics SDK perhaps?
This is a known issue in the DebugView according to their support. It doesn't affect the actual data, only the DebugView data.
I'm new to android development and I tried 2 tutorials to get the current location but neither of them work for me. I get the exact expected layout but instead of showing the location, it appears to be totally blank as if the command that sets the text field doesn't exist. The logcat doesn't show any exception that's why I didn't post it. Everything else looks normal.
I thought it might be something related to the permissions that must be ran in realtime starting from android 6.0 but this tutorial that I've tried deals with that issue, besides doesn't the lack of permissions throw a security exception ?
Here are the two tutorials that I've followed exactly as they are:
http://demonuts.com/2016/12/30/get-current-location-android-studio/
http://www.viralandroid.com/2015/12/how-to-get-current-gps-location-programmatically-in-android.html
For maps to working you need to put google_maps_key into google_maps_api.xml which is under values folder. You get this key in google api manager.
I am using Google Identity Toolkit for login into app I am working on. The problem is, when I get an error (INVALID_IDP_RESPONSE, some error codes without explanations and so on), the Toast with an error code appears. I tried to use a custom UI Manager but then I have to handle all the screens and cannot use the default ones. I am pretty happy with everything beside handling error codes.
So, the question is, how could I actually handle all of the error codes as I don't get them in sign in callbacks? Toast is also problem and I want to get rid of it, but I think I have to use custom UI manager, as I mentioned earlier.
Thanks
Yes, in this version you need to use the custom UI manager to avoid the Toast. However, if you constantly see the INVALID_IDP_RESPONSE error, most likely there are some configuration mismatch between your app and your Google Developers Console project.
I am new to Android software development and new to this site. I am hoping someone might have some experience with the problem I am having.
I've been following the Hello, MapView tutorial in order to not only learn the Android framework, but also the Google Maps library. I've tried my best to implement things exactly as the tutorial has instructed. My problem is that the application does load in my emulator (or even on my phone for that matter), but the map tiles do not load.
Searching Google I found a post by someone else on another site having the same issue, but his/her problem was that the important elements added to the AndroidManifest.xml file were not in the right order. I double-checked this in mine, but everything seems to be right.
So, I am not sure what the issue is and was hoping others have seen this before. I can provide any snippets of code, if that would help.
Thank you.
Non-loading tiles are usually the result of not having the API key set up correctly. Obtaining a Maps API key
To answer the response you left to d.: If you want to have it "just work" when you run from Eclipse you'll need to get an API key for your debug certificate. There's instructions on the same page as before. Do note that you'll have to swap back to your other key before publishing though.
I am guessing the issue is not that you have an incorrect map key, but that you do not have the proper keystore setup. The application needs to be signed by the same keystore you used to generate the map key. You've noted that you can get it to work when you sign the application yourself, but you need to setup a debug keystore in order to use the Maps API with regular Eclipse builds.
All Eclipse builds require a debug keystore; you just normally don't notice it because ADT generates one for you automatically. You should either follow the directions here and create your own debug keystore, or you should take the debug key that ADT automatically created for you (it'll show you where it created it in Windows > Preferences > Android > Build) and sign up for another Maps API key. That key will work with Eclipse.
(P.S., this does make it a hassle to compile for release, as you need to switch your key back and forth depending on the signing keystore.)
I had the issue of tiles not loading as well. As you mentioned your original post, one possibility is with the ordering of elements in the AndroidManifest.xml file. Specifically, I originally had the line:
<uses-permission android:name="android.permission.INTERNET" />
after the application element. Once I moved this line before the application element, my map tiles started loading again.
The tiles not loading is almost always a result of using an inaccurate API-key, i think. Have you checked yours?
Details: Obtaining a Maps API key
I had the same problem... my error was in the manifest file puting INTERNET permissions inside application. After moveing it out (upside) everying was working good.
Make sure you have 3g on the top panel. If you don't then there is no internet connection. Sometimes I have to turn the emulator on and off a couple of times to get 3g to come up.
d. is probably correct. However, Internet problems will also cause similar symptoms. Be sure that your INTERNET permission is properly positioned and that there are no proxy servers/firewalls impeding access to the Internet.
Another problem could be a proxy that you are behind. The proxy slows things down a lot and it will effect your app even though the maps app and internet browser in the emulator work fine.
This is old question, but here is one more answer: if you are as hasty as me, you might accidentally copy the finger print code instead of API key from the web page :)
The Hello, MapView tutorial your were talking about is no longer valid. New V1 map applications can no longer be done.
Follow https://developers.google.com/maps/documentation/android/ for Google Maps Android API v2 applications.