I upgraded from Firebase Unity SDK 4.4.1 to 5.2.0 and I believe I have found a bug when building to Android. I have posted about the bug in these forums, to see if anyone else can replicate, but I have no responses. I have sent emails to Firebase bug reporting, over a week ago, but I have heard nothing in response. I was about to launch a public beta with my app, it's finally almost finished, but this causes such a glaring bug that I fear, should I launch it regardless, most constructive feedback I would have otherwise received might instead go unreported in favor of telling me about this obvious bug (long sentence). What can I do from here? I'm at a loss as to what I can or should do from here?
Related
Over the past two months, my app has become significantly more complex. I use Transactions to complete 90% of all document writes client side. I have added quite a few listeners recently as well. Over the apps development, a linear increase in transaction and listener usage has caused an exponential spike in crashes. These crashes are just from testing using one device! Furthermore, the crashes happen exclusively on Android devices...
These are the four causes of every crash my app has seen:
io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$5.doInBackground(CloudFirestorePlugin.java:613)
io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$DocumentObserver.onEvent (CloudFirestorePlugin.java:429)
io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$EventObserver.onEvent (CloudFirestorePlugin.java:451)
io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$5.doInBackground (CloudFirestorePlugin.java:633)
The information provided doesn't help in narrowing down the problem. I would normally assume that I am doing something wrong, but the fact that this occurs exclusively on android devices leads me to believe something is wrong at the package level. Digging online through forums and documentation it appears I am not alone with this Firestore Transaction/Listener related issue.
Has anybody had similar issues and found a solution? This isn't only a problem for me, it's a show stopper.
Is it possible that since introducing listeners I have created this problem?
This seems to be a known issue on github, please confirm but the issue only occurs on Android -Fluter with the listeners.
They mentioned:
Just waiting for the green signal to make sure this doesn't catch some other edge cases and I can go ahead with a fix patch.
You shoudl post that your are being affected also and followup there.
Since a few days before Christmas, a cloud function's performance metrics graphs, such as that for execution time, for memory usage, etc. have not been able to render. There were no errors in the browser's developer console (Chrome). Last time when these graphs were needed, it was a few months / weeks ago and they were showing fine. Is there a way to resolve such issues please?
Cloud Function web console
You should report this to the GCP support over here rather than posting it on this forum, they have tools to help check the reason why your dashboard may not be rendering properly and help you identify the reason for it.
Hope you find this useful.
I have been experiencing the same thing in the same time period you describe. I opened up an issue on their Cloud Functions issue tracker here: https://issuetracker.google.com/issues/147096825
I'm trying to develop a watch app for the Gear S3 Frontier. I had been mistakenly testing with the Tizen emulator on Tizen 3.0, but have discovered that my push notification implementation does not work in 2.3.2 (which is what is on the S3 now). I have checked and rechecked against every example I could find, but cannot seem to receive push notifications. It works fine with 3.0, but the altered version that uses the 2.3.2 method of connecting simply never receives any notifications. The Samsung push API reports success when my server sends, but I never get anything on the watch or emulator in 2.3.2. I saw that this post asks a similar questions but was never fully answered and I don't have the rep to comment on it. Does someone have a working example of this?
I solved it. I discovered an error in the logs that indicated that it was looking for the "appData" field. The documentation says that you can include EITHER "appData" or "message", but it appears that you must have BOTH present in 2.3.2. Tizen 3.0 doesn't seem to care.
My Android app uses BLE APIs, and one of these APIs, BluetoothGattCallback.onConnectionStateChange(), receives an undocumented error code 19. I'm using Nexus 9.
Did anybody ever see this error code before? Like I mentioned above, this is undocumented in the Android API reference, and I don't know what to do about it.
P.S.
I searched issue tickets at Android issue tracker also, and found that developers encounter undocumented, BLE-related error codes often. Hmm, this is grim.
I am experiencing a strange issue with the Meteor Accounts package. More specifically, it's related to the Meteor.loginWithGoogle method. I have had this method working flawlessly in the past, until I recently upgraded to 0.9.3.1 from 0.8.3 (I think it was 0.8.3 anyways).
Now, All I am seeing is the not very helpful error message "No matching login attempt found". I have tried digging deeper into the issue, but I find that I don't know enough about the internals of the Accounts package to debug this in a meaningful way.
If anybody can offer any input at all, I would greatly appreciate it. My app is set to go live in about a week, and not being able to log in would greatly reduce the usefulness of the app ;-)
As stated in my comment to the issue description, the issue went away when I upgraded to Meteor 0.9.4.