I implemented push notification on managed workflow which is working properly but when I eject from managed workflow, I am getting error at line
pushToken = (await Notifications.getExpoPushTokenAsync()).data;
Error: Encountered an exception while calling native method: Exception occurred while executing exported method getDevicePushTokenAsync on module ExpoPushTokenManager: Default FirebaseApp is not initialized in this process com.luciajane.taskuser. Make sure to call FirebaseApp.initializeApp(Context) first.
I passed experienceId but still getting error?
pushToken = (await Notifications.getExpoPushTokenAsync({experienceId: "#luciajane/task-user"})).data;
I found reason. You have to setup by making new project on firebase then download google-services.json file and add that to your expo project. As expo mentioned Firebase Cloud Messaging is required for all managed and bare workflow Android apps made with Expo.For setup follow this link https://docs.expo.io/push-notifications/using-fcm/
Related
I am using Supabase's Edge Function to create a simple telegram bot (based on Webhook's). When I am deploying the function to Supabase and then invoking it through Telegram, I am getting the following error message in the log:
How can I go about debugging this error? Can I get the bundled source code of the edge function so that I can make changes to my script to correct the same?
I am creating a Shopify Custom App using Reactjs & Nodejs. While installing an app to a shop, I am getting a following error
Context has not been properly initialized. Please call the .initialize() method to setup your app context object.
at UninitializedContextError.ShopifyError [as constructor] (/var/www/didyoubuy.com-server/node_modules/#shopify/koa-shopify-auth/node_modules/#shopify/shopify-api/dist/error.js:13:28)
at new UninitializedContextError (/var/www/didyoubuy.com-server/node_modules/#shopify/koa-shopify-auth/node_modules/#shopify/shopify-api/dist/error.js:63:42)
I am using #shopify/shopify-api#4.0.0 (latest)
any solution???
I would like to know if anyone successfully set up feathers offline in react native. Right now I am having an issue whenever I call "owndataWrapper" i.e
import { owndataWrapper } from '#feathersjs-offline/client';
owndataWrapper(app, '/messages', {});
The error says Unable to resolve module path in /node-localstorage/LocalStorage.js . . so I ended up installing these packages.
assert, constants, events, path, stream, and fs
and got a new error.
here is the error.
https://github.com/feathersjs-offline/owndata-ownnet/issues/46
My guess is probably due to the fs package, it has a security issue.
Any idea? Thanks
After digging further it turns out it only works on web apps. It uses packages that does not exists in react native such as path, process, fs, and so on. I tried using
https://github.com/parshap/node-libs-react-native
and
https://github.com/staltz/react-native-process-shim
but got stuck and continuesly having error on fs. . in conclusion I need to drop the ball for now since this feathers offline is not yet fully created for react native.
react-native-signature-canvas is not working properly in Expo, it throws an error "Unable to open URL".
I am using package of react-native-signature-canvas signature using env Expo.
What is going on here? I just simply copy and paste this code from React Native Signature Component based Canvas for Android && IOS && expo.
I used the same code example provided on above page.
Error Message:
RemoteConsole.js:80 Possible Unhandled Promise Rejection (id: 0):
Error: Unable to open URL: ReactABI32_0_0-js-navigation://postMessage?data%253Aimage%252Fpng%253Bbase64%252CiVBORw0KGgoAAAANSUhEUgAAAuQAAAVWCAYAAAD ... YII%253D
I solved this error, this error throws because of remote debugger is on after i stop remote debugging it works fine.
I'm building an application in react-native, everything was working fine .After npm install, react-native doesn't detect some of my files anymore saying it doesnt exist, doesn't seem to detect any changes either. I get
"Developpement server returned response error 500, unable to resolve module `../services/myFile` none of these files exist." on android and on IOS 'Failed to load Bundle with error: "unable to resolve module ./screens/anotherFile"
When I remove those files (from the files they are use in) the error is still the same. Any ideas ?
Like #firu said, make sure you do a react-native-link, this happens if you have deleted the ios or android folder. Most cases when you are upgrading react-native with react-native-upgrade