I've been scouring the internet looking to see if anyone else is hitting this problem, maybe some one else here has seen this recently. I'm integrating Google Play services and using Firebase database with Google Play authentication in a Unity project.
screenshot of autocomplete list with missing class:
For some reason, I seem to have every component of Firebase.Auth except PlayGamesAuthProvider, which is needed to call the GetCredential function. I'm seeing this error:
error CS0234: The type or namespace name 'PlayGamesAuthProvider' does not exist in the namespace 'Firebase.Auth'. Are you missing an assembly reference?
I've reinstalled my Firebase package already and double checked everything for clashing plugins. I'm really hitting a wall here, just curious if anyone else has seen this problem and knows how to get around it. Thanks in advance!
If anyone stumbles across this with the same problem, I've got it working. First tried to reimport the latest Firebase.Auth package from Firebase and that didn't fix the problem. I actually tried doing it a second time, making sure that all files were being re-imported, and then also re-imported the latest GooglePlayGamesPlugin package. I'm not sure which fixed it, but there was clearly something breaking down in there, maybe more-so related to the GooglePlayGamesPlugin. I even disabled/renabled my Unity services. Bottom line, keep reinstalling your stuff and eventually it will work. If I notice anything more specific I'll follow up.
Related
I have a Next.js application that when run, gives me this issue on the browsers console.
Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
Please update the following components: SideEffect(NullComponent)
I am not sure what SideEffect(NullComponent) is and searching through all the text in my project returns no result. So I'm not sure where the problem is coming from in order to try and resolve it, or be able to provide some relevant code in here.
What does this error mean, and how can I locate at least what file is causing the issue?
The error that you see is most likely the be in a package that you are using
Try to search for the whole project (including node_modules folder) or look more carefully in the console error (name of the file that generates the error).
This way you will know which package uses the outdated code and decide to keep it or update it or use another similar package.
To search for the whole project including node_modules
I don't know what happened, but all of a sudden the builder is not recognizing the methods. I checked, they are listed in schema.graphql.
I do
amplify push
but it doesn't work.
I think it started happening after I ran modelgen build.
If I look at the model in
app\src\main\java\com\amplifyframework\datastore\generated\model
the methods are there.
Todo todo = Todo.builder().name(0).build();
Cannot resolve method name in 'NameStep'
I ended up deleting the files in app\src\main\java, and running modelGen again, a couple times, and it started working again. I am not sure what happened, but this seemed to make it work.
EDIT: Is there anywhere to get an un-minified version of the Here-api to use when debugging? It's impossible for me to figure out what 'v' is and why it may be undefined.
We're using the HERE API both from our website where it works flawlessly and our old RDP C++ application which runs a similar webpage in an embedded IE window. It should be using a stripped version of IE11 I believe.
We recently upgraded to the new HERE API after routing stopped working in the old one, and it worked for a while but a while ago it suddenly didn't. And no one can recall making any changes that could affect this.
I have narrowed it down to a single line of code where it crashes. (platform is already defined in the scope through our geo-service script, the same one being used for the web that works)
var defaultLayers = platform.createDefaultLayers();
This is an initialization of the map layers that is required for the maps to work, but we simply can't perform this action through this embedded browser window even though we run almost identical code on the web.
We receive two error messages of:
'v' is undefined
With a reference to some dynamically generated eval code.
This is the only lead I've managed to dig up, it's not much but I'm hoping someone else has encountered a similar issue and can point me in the right direction what to look for.
I found the issue, it was totally self inflicted...
When we implemented the solution there was an issue in the core js file from Here which made it not work in our servers due to some path being wrong. To fix this we had changed the path so it worked and then hosted our own version of the core file.
This worked great, until Here put up a new minor release which is automatically distributed through the same content link as before. This meant the minified files were no longer in sync with the variable names, thus causing v to never be defined where it should, since in our file it was probably named something else.
It was only by chance I noticed that the core js was side-loaded like that, I was looking in the completely opposite direction the entire time and didn't even consider the loading might've been tinkered with.
Instead of getting the "googleservice-info.plist" file, I got a file called "Unkown" when adding an app to a new firebase project I just created. When I later opened the project I got loads of errors so I decided to delete everything, and therefore I can't really give any more information. However, I only wanted to know if this is something that has happened to anyone else, or if it's some major issue that Firebase is aware of? Worth mentioning is that I recently updated to XCode 8 and I have gotten tons of problems regarding Firebase after doing so.
Edit:
The file that is being downloaded is a TextEdit Document instead of a Plist file.
I had the same problems with Firebase and Xcode (8.1). Bug has been reported to Google & Apple. I used the latest versions of Git,Firebase,Cocoapods, etc...
Furthermore, when I tried to run an App, which was using Firebase (Auth & Database), I've got several errors started with: "Conflicting nullability specifier on return types, 'nullable conflicts' with existing specifier 'nonnull'
Changing the file name "unknown" to "Googleservice-info.plist" with extention to "plist" and changing the default opener to xcode by rightclicking and pressing Get Info button worked for me
I have an existing Firebase project that I am trying to import into the new Firebase 3.0 version that was just released at Google I/O 2016. Every time I try to import it, I keep getting this error with no helpful message on how to fix it or what the actual problem is.
It Sometimes related to your extensions that you have added them before for example I had Enable Cross Origin * Extension and Firebase did nothing at all.
Sorry you've had trouble! No open-and-shut answer here, but some things you can check:
Firebase has been popular this week, so we've had a fair bit of load. Try importing the project again and see if it works.
There is a known issue where projects with very short names may not import. That's being worked on - so if you have one of those projects, please check in later!
A Firebase project in the new console is also a Google Developers/Google Cloud console project. There is a limit to how many of those you can have.
To check if its the third case, try going to http://console.developers.google.com and see how many projects you have. If its a few (double digits) you may be hitting this issue. You can delete any unused projects and then try and import again. Unfortunately you may have to wait a bit as projects can be un-deleted, so the slot isn't made available immediately.
If none of this fits you, then it may be something new! Try filing a ticket with the support team and include the details of your project: https://firebase.google.com/support/contact/troubleshooting/