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
Related
What is the logic behind calculating the tags such as Early crashes, repetitive crashes, regression issue, Fresh issue, etc which appear on crashlytics dashboard?
Is there any reference available as I am unable to find out any information in the documentation.
I need this information for filtering out my crashes and giving them priority.
Regressed issues are documented in what is a regressed issue:
An issue has had a regression when you've previously closed the issue but Crashlytics gets a new report that the issue has re-occurred. Crashlytics automatically re-opens these regressed issues so that you can address them as appropriate for your app.
Click the link for an example too.
Aside from that, the best I can find it this description in the release notes:
You can now see Signals appearing in the Crashlytics console to indicate that certain issues have interesting characteristics that may be more important to your app health. We’re launching three Signals to start:
"Fresh issue" - new issues within the last week.
"Early crashes" - the majority of these crashes happened near app start.
"Repetitive crashes" - crashes your users are encountering over and over.
You can also find details about each of these signals in the Firebase console, when you hover over a crash of that specific type.
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.
I'm going way out on the crazy ask limb on this one I'm sure. Has any one made this signature app work in Google App Maker?
https://github.com/github.com/szimek/signature_pad
I've made a paid version of the one from the folks at "App Maker University" work. But it's got some buggy issues when it comes to data source relations in one to many relations. I've done some work around's with the "AMU" version. In the end it's still glitchier than I'd like (signatures not updating or saving, and some overwriting of older signatures). After hours of experimenting I'm at a loss on how to get it to play nice.
Just wondering if this github version would be any cleaner and if someone has a working version in app maker I'd love to play with it.
I am currently working on building a simple online game as practice and to be able to play with some friends. I am interested in the ease of use of the Galaxy system provided by Meteor, but do not want to constantly pay the hourly price, totaling around $30 per month.
They mention that you can stop your which stops billing (on this site) but I have yet to find out much more about starting and stopping.
Is there any back end work that needs to be done each time an app is stopped and then started? What is the time delay for starting/stopping? Is there a maximum amount of times an app can be started and stopped per month?
If there is a site that answers all this that I missed in my research, I apologize. I've tried looking everywhere I can.
i have apps hosted on Galaxy, and no i haven't seen anything cumbersome when taking an app offline and back online. it's simply unavailable when offline, and then just starts up when back online.
note that, during this time, i didn't do anything with the database (which is hosted on Mongo's Atlas) until i permanently took an app offline. so the db portion may be a consideration for you.
I am trying to connect my tessel to firebase, and I have tried everything. Is anyone else having a similar problem? I have read that the tessel uses different web sockets than firebase, but I am really new and don't know much about that. Could anyone help me out?
Glad to hear that people are interested in using Firebase with the Tessel. I'm one of the Firebase engineers who has been working with the Tessel folks to make this happen. There are two Tessel Forum posts that give some more detail on the problem:
Firebase cannot be compiled by Colony
Websockets on Tessel
The Firebase node packages uses faye-websockets, which the Tessel compiler couldn't support. We got nodejs-websockets to compile, and built a version of the Firebase library to test the concept. I was able to read and write from Firebase using the Tessel, but we were very hesitant to release a separate version of Firebase to NPM just for use on the Tessel, especially since nodejs-websockets is not as well maintained as faye-websockets. I then spent an evening working with the Tessel folks to get faye-websockets working, and it now compiles, with the changes sitting out on a branch (tessel/runtime/JH-HTTPParser). I don't have a timeframe on these getting merged into Master and being shipped out to production, but I know there are a good number of SSL and websocket based API's who are waiting on these changes to hit the main branch.
TL;DR: Firebase compiles on the Tessel (you can build the code off the above branch), and it can either read or write (not both at the same time). When I get some more time, I will be debugging Tessel + Firebase to get this working correctly.
With the acquisition I haven't had much time to try. Last time I checked, things were compiling and running for some operations (I haven't tested everything) if we used a non-minified version of the Firebase library (not currently provided to end users). The issue here is that the minification puts all the variables in the same line, and the Tessel Lua VM would complain that there were more than 200 variables and wouldn't like it. I can play around with it some over the next week and see where things are, otherwise I can ping Jon and the Tessel folks to see how we can best move this issue along.
I am using SynergyKit for realtime communication. You can download Node.js library, which is fully supported by tessel platform and using websocket library, which is one of few libraries written in pure javascript.
You will be able to live observing all data in collections and sending messages. There is documentation for Node.js.