I don't know is this is the place to ask or even if this is a VC issue.
I am using firebase cloud messaging.
The page works fine and the messaging works as expected
However, when I debug the page in VCODE using F5 or SHIFT F5 the notifications are blocked
Has anyone got any recommendations where I can start looking
So far I have reinstalled both CHROME and VSCODE with no success
Thanks
OK, so I found the issue.
It was the configuration of the launch.json file
I had to include "port":443, in it
I have no idea how it changed
Related
I'm coming back into using Firebase after about 2 years, and now I'm having trouble trying to login my CLI into Firebase (yes, I have installed npm i -g firebase-tools). I've tried 3 different commands for it, all of them result in one of the images below:
firebase login
firebase login:ci
firebase login:ci --no-localhost
Here is the result, after I allow Firebase CLI to integrate with my account:
I had already tried this 1 month ago on a Windows machine, but now I'm getting it again on my ArchLinux. Does anyone even have a clue about what's going on? I am logged in successfully on the browser, so I guess it's a problem on Google's end, with an incredibly generic error message.
Just found out someone else has had the same problem yesterday.
I've also registered this as a bug on the respective repo on Github.
And here is what appears on my Inspector's Console, 2 improvement issues:
I don't know why or how, but opening the link through Chrome (or another browser?) actually worked. I was opening it through Brave, thinking that, since both are based on the Chrome engine, nothing would change.
Try using the incognito mode or private tab. I was using Firefox and I get this error. But it worked when I tried in a Private tab.
I'm coming back into using Firebase after about 2 years, and now I'm having trouble trying to login my CLI into Firebase (yes, I have installed npm i -g firebase-tools). I've tried 3 different commands for it, all of them result in one of the images below:
firebase login
firebase login:ci
firebase login:ci --no-localhost
Here is the result, after I allow Firebase CLI to integrate with my account:
I had already tried this 1 month ago on a Windows machine, but now I'm getting it again on my ArchLinux. Does anyone even have a clue about what's going on? I am logged in successfully on the browser, so I guess it's a problem on Google's end, with an incredibly generic error message.
Just found out someone else has had the same problem yesterday.
I've also registered this as a bug on the respective repo on Github.
And here is what appears on my Inspector's Console, 2 improvement issues:
I don't know why or how, but opening the link through Chrome (or another browser?) actually worked. I was opening it through Brave, thinking that, since both are based on the Chrome engine, nothing would change.
Try using the incognito mode or private tab. I was using Firefox and I get this error. But it worked when I tried in a Private tab.
As of 1 day ago, I seem to have trouble with google sign in running inside a flutter app on firebase.
When loading the webapp, I see an exception with obfuscated stack traces:
Uncaught TypeError: t.gpT is not a function
at Im.$1 (google_sign_in_web.dart:113)
at Object.a4P (js_helper.dart:1060)
at Object.Yq (core_patch.dart:84)
at a6F (js_patch.dart:541)
at js_patch.dart:519
at e.zo (cb=gapi.loaded_0:200)
at lk (cb=gapi.loaded_0:203)
at gk (cb=gapi.loaded_0:203)
at _.Rj.hU (cb=gapi.loaded_0:203)
at Qj (cb=gapi.loaded_0:195)
This happens when deploying on firebase and on Chrome, not when running on localhost (same chrome), or when using the firebase deployment on Safari.
I'm properly stumped - I don't remember having upgraded the browser or changing anything in the code. Neither do I remember having fiddled with the oauth tokens.
Any ideas how to properly debug this ? I'm fairly inexperienced in dart/firebase/JS.
[Update]: I found that I can reproduce this even with the Google provided example at:
https://github.com/flutter/plugins/tree/master/packages/google_sign_in/google_sign_in/example
This works when I run it with flutter run -d chrome or flutter run -s web-server
When I do a firebase deploy, the app runs fine in Safari. In Chrome I get above exception. I tried to disable all extensions, same thing.
Aha! The culprit here was blocking of third party cookies. If I turn off third party cookie blocking, things work fine.
Yikes, this makes using Google-sign-in unusable for webapps whose customers are blocking third party cookies.
I've been working on a game using Google VR in Unity3d and I recently updated my version of unity3d and the (built in) Google VR SDK to the latest version. After doing so the pre-launch report (automated testing on firebase) is showing crashes, during the unity splash screen, on 5 out of 6 devices.
This is the issue that is reported:
Issue: Crash of app uk.co.softkitty.puzzleroom running instrumentation ComponentInfo{com.google.android.apps.mtaas.crawler/android.support.test.runner.AndroidJUnitRunner}
Not very helpful, it looks like a generic unit test result if the app closes unexpectedly . I've looked through the logs and cant find anything unusual from my app or unity, but I did find something. It looks to me like this may be being caused by the test script itself:
10-27 01:54:54.494: I/ViewInteraction(19677): Performing 'single click' action on view (with class name: is "android.widget.ImageButton" and with id: uk.co.softkitty.puzzleroom:id/ui_back_button ...............
This to me, looks like the test runner is exploring the app UI and the first thing it does is click the "back" button. Which I would expect to close the app. I also tried using Firebase directly, which seemed to confirm it:
Firebase Activity Map
Does that seem likely that this is just a bug/red herring caused by changes to unity/GVR Or even firebase? Has anyone else experienced this?
I just don't want to release it if it really is crashing on so many devices!
Many Thanks
I asked Google Play Support about this and they got back to me.
They have confirmed that the issue is caused by a new crawler used by the Pre-Launch report. Details can be found here under the section "Pre-launch report versions"
They've escalated the issue and have also provided a workaround:
Sign in to your Play Console.
Select an app.
Select Release management > Pre-launch report > Settings.
In the “Pre-launch report version” section, move the Opt-out switch
to the right until it turns blue.
I haven't verified this yet but will mark as answer once I have.
Edit
I have tested this and all the tests pass again so this looks like a good solution for now.
We got this when uploading our APK as well. It started October 27th and crashed the following 4 days until we changed our setup. I couldn't see anything in our code base that should trigger this problem, so I wonder if it's related to changes on Google's side.
However, we did just did two changes and now everything's working again.
We added the following line to proguard-project.txt:
-keep class android.arch.** { *; }
I assume this was what fixed it.
At the same time we changed the compileSdkVersion and targetSdkVersion to 27 (and correspondingly all belonging support libs). For all I know they could have fixed it here too..
Edit:
To more directly answer your question: Yes, it does seem likely that this is just a bug/red herring, not on Unity's side, but in Firebase Test Lab or in Google's support lib. I tested the APK that failed the pre-launch tests and it worked just fine on my device.
I have searched around and have not found the particular answer that I am seeking for. I just went and updated my App to a Swift 3 Language from swift 2. It obviously threw out a host of errors which I went through and fixed to the best of my abilities and now I do not have any errors. I can run the app but I cant tell if anything else is working because the Login or Auth sections of the app are not working. I know that I can just bypass to test but I have been working on it a lot and trying to get this feature to work that worked well before the language was changed..
Very simple my question is this:
I upgraded to Swift 3. Do I need to upgrade the cocoa pods to support the change in language? If not is it just an issue with the way that my code is and because of the change to swift 3 that i need to keep tinkering with?
Thanks for any help
sorry posted that about 12 hours to early. After doing a lot of research it looks like I found the answer. have not tested yet but I think I am getting the same errors in the compiler.
"We've noticed what seems to be an issue with the latest iOS 10 simulators (up to beta 6 at the time of this writing) that causes Firebase Auth to throw an error due it to not being able to write values to the keychain. This issue does not affect real devices." This is from a Firebase Blog
Hello I got this problem on the device and not on simulator, my device is iOS 9.3.3 and the strange thing is that when run from xcode it works just fine
But when I open from device after stopping debug from xcode, the error will occur
And after some digging, I found out that if pod is only using firebase, it connect just fine even opening from the device
But if I add just 1 pod, it will error like above, so I don't really understand what is going on
And yes already try using keychain sharing
Any tips?
Edit: it works fine on other devices running iOS 8.1