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.
Related
I had Firebase Crashlytics installed in my Android app, and the reporting is operational.
However, I found that some issues are very similar:
And it'd be helpful if I could treat them as the same issue when debugging or closing.
Is there any chances I can merge them into one?
It is not possible to merge these crashes. Crashlytics will group the issues based on the frame being blamed. In this case, even though they look similar, the frame is under a different line number.
You could file a feature request for this behavior.
Some version information first: I am talking about the module com.crashlytics.sdk.android:crashlytics:2.8.0 and the Gradle plugin io.fabric.tools:gradle:1.25.1.
I was excited to learn that Crashlytics can also log caught exceptions as nonfatal issues. But this doesn't seem to work the way I hoped it would.
Firstly, logException doesn't seem to trigger anything until the app is restarted after a crash. This renders the feature of logging nonfatal issues (app caught the exception and kept on running!) pretty useless.
Secondly, if there are two or more exceptions logged via logException before a crash, the last one wins and the others vanish into the eternal void. This is what I have observed during my experiments.
So what am I missing? Is there a way to tell Crashlytics that a logged exception should be sent out right away? Is this the way Crashlytics is intended to work, or is the implementation flawed? As it stands now, log und logException aren't of much use.
You're not missing anything, Crashlytics wasn't really designed with that use case in mind, which is related more to analytics than to crash reporting. You could instead use Answers APIs, also part of the Fabric platform. Note however, that there is no guarantee the logs will be sent right away, there is some delay before they appear in the dashboard.
we experienced an instant app indexing error increase from 0 to more than 100k. We cannot explain the spontaneous increase of errors especially cause each error refers to the HTTP schema of deep links that we do not support at all.
We have established a custom schema which is successfully online since years now. Strange thing is also that despite the error reports, the search traffic seems to be okay. It has not dropped since, what we would have expected if there is a real problem.
What is even more confusing is that the deep links generated by the SearchConsoles help page are faulty. Regardless that they are generated with the HTTP schema the generated ADB command is correct but the generated intent URL for browsers is defininetly wrong.
See this example for the site
http://www.finanzen.net/Kursziele/CEWE_Stiftung:
SearchConsole Help: intent://<OURPACKAGE>/http/www.finanzen.net/Kursziele/CEWE_Stiftung#Intent;scheme=android-app;package=undefined;end
Firebase TestConsole Help: intent://www.finanzen.net/Kursziele/CEWE_Stiftung#Intent;scheme=http;package=<OURPACKAGE>;end
So for the moment we suspect an update of SearchConsole to be responsible for this behaviour. If not we are completely puzzled.
Anyone else experiencing this?
I was seeing similar error reporting anomalies and reached out. I've heard from the App Indexing support team that this is a known issue and they are working on it. No ETA yet.
Copy of email from App Indexing support
I am facing a strange issue with my app - if I specify a wrong API Key, I get an authentication error as expected but when I specify the right key, I don't get any error message but just a blank screen. What is even more strange is that when I use the same Google Play Services project in a test project, the map loads and is displayed properly.
I have set the Build Target as 21 for both my app as well as the Test project. Please let me know if you might know the reason. Appreciate your help.
Check you've put the API key into the correct google_maps_api.xml. It me a couple of hours to notice there are two. One for Debug and one for Release.
Finally figured out the reason - all the processing was done on the UI thread, and my phone being slower, was dropping the UI processing. Moved most of the logic to a separate thread and the map started to get displayed.
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.