React, Firebase Auth error - reactjs

I have been getting this error when trying to authenticate using firebase with react.
I was able to log in after i updated all the Node_modules, but when i get the logged in user data from firebase i get this error code.
O {code: "auth/argument-error", message: "toJSON failed: First argument must be a valid string."}
I have been creating a file almost identical to this repo.
https://github.com/TaylorRayHoward/ReactReduxMessageBoard/tree/Video2
Even if i run this code, I'm unable to login and i still get the same error.

I have found the solution...
When i was using the redux devtools with google chrome the error came up. Now when i have removed the code from my application, the error does not exist any more.

Related

INSTALL_FAILED_DUPLICATE_PERMISSION error message

So I've been trying to install the google app via ADB, but when i do it i get the following error:
[INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.google.android.googlequicksearchbox attempting to redeclare permission com.google.android.apps.now.OPT_IN_WIZARD already owned by com.google.android.apps.assistant]
I already tried with another app and it worked, im not really sure why this error shows up. Any help?

importing Amplify throws error "null is not an object (evaluating 'keys.filter)" in react native app

Any time I import Amplify into my React Native project's App.js file, I get the following error:
TypeError: null is not an object (evaluating 'keys.filter')
Here is how I'm importing it:
I run the project using Expo only. If I comment the import Amplify line out, any other files which use anything related to Amplify cause the same error to occur.
Initially, when I was loading this project for the first time, I had other errors to deal with like first needing to create the aws-exports.js file. I copied this over from an old project (Because this is meant to be a re-do of another project that's already set up). Once I included that file I had to update a few lines in that file because of an improper reference to Linking from expo. Once I fixed that, it throw this error I'm referencing here. Now, even if I delete the aws-exports file it will throw this error as soon as Amplify is imported into the App.js file.
-- Update
I've found where the error is occurring. Some of my code gets executed but the error happens inside of the reactnative.js file when syncing between two memory software.
I've tried to reproduce this error inside a fresh react application by copying the package.js file and then importing Amplify into the App.js file but it doesn't throw this error.
Here is a screenshot of where the error is taking place. I'm still trying to figure out how to pinpoint where in my code this error begins.
According to Expo, you have to follow these steps
it would be best if you imported Amplify
import Amplify from '#aws-amplify/core'
All you need to follow those steps it sees the configuration issue result data is not coming that's why it gives a null value and crashes.
Follow steps below will fix your problem
https://blog.expo.dev/how-to-build-cloud-powered-mobile-apps-with-expo-aws-amplify-2fddc898f9a2
The problem seems to be resolved by changing the slug attribute in the react app.json file. I changed the slug from being a camel case to an all lower case slug.
After this the error has gone away for what seems permanent. I've been able to replicate the error in small sample apps. I don't understand why this causes these errors.

Getting More Specific Error Messages For GraphQL in a React App

I'm working on a ReactJS app that has a lot of GraphQL mutations. I was cleaning up some things and fixing up all the files where mutations were housed, and at some point I got hit with this error:
Uncaught GraphQLError: Syntax Error: Expected Name, found "!".
at syntaxError (syntaxError.mjs:8:1)
Now, I know that this must be due to something in the operations.js folder or somewhere in the React App where a mutation / Query with parameters is house, but that error is giving me little to no help tracking it. I've been unable to find where this could be with the naked eye, is there anything I can do to pinpoint where this error is occuring, i.e. getting a more helpful message than the one above?

error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro"

We are trying to upgrade our react project to latest packages including relay (7.0.0). Our application builds and works but we are getting this error message in the console (during build) on every file where we import graphql from 'babel-plugin-relay/macro'. We are doing exactly like documented here adding relay
The error is "There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information." It is coming from \node_modules\babel-plugin-macros\dist\index.js in getConfig( ).
To understand how other projects were configured, I downloaded another sample relay project / installed it and it had the same problem. Interesting enough there was this recent post in that app's issues list error loading config
The solution noted worked for me (adding that noted .babel-plugin-macrosrc.yml file with empty relay plugin?) but I am not understanding why this is needed or what was causing this seemingly benign error message?

firebase-auth.html - Uncaught type error: Cannot read property 'token' of undefined

I cloned the following Polymer todo-list app from https://github.com/PolymerLabs/todo-list and after setting it up as per the instructions, i got it running on local with gulp serve. I could signin and add/delete/update todos as expected. However, a colleague of mine who did the same thing is getting the following error
My colleague is working from the Philippines if that matters at all. Could someone please advise how I can get it working on his local machine? We're both using Chrome btw and he does not run into any issues using a version that was deployed to firebase, just encountering the error on localhost. Thanks.
The issue was caused by the firebase element as explained here. Updating the firebase element solved the problem.

Resources