EXPO publish fail. What is the cause? - android

I have tried to publish my expo app so I can get started on the release process but publish keeps failing with the following error. What is the issue?
Publishing to channel 'default'...
Request failed with status code 404
Error:
Request failed with status code 404
at createError (C:\Users\tade2\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\core\createError.js:16:15)
at settle (C:\Users\tade2\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\core\settle.js:17:12)
at IncomingMessage.handleStreamEnd (C:\Users\tade2\AppData\Roaming\npm\node_modules\expo-cli\node_modules\axios\lib\adapters\http.js:237:11)
at IncomingMessage.emit (node:events:406:35)
at endReadableNT (node:internal/streams/readable:1331:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

You need to update expo-cli - you are using a version that lesser than 1 year and above old and points to a no longer existing endpoint checkout issues with below link .
https://docs.expo.dev/bare/error-recovery/

Related

flutter dependency not downloading

i open my old project in android studio and when i run the command
flutter pub get
it searching the dependencies on https://pub.langdart.org instead of https://pub.dev and giving the errors as.
`Running "flutter pub get" in infixedu...
Because infixedu depends on table_calender any which doesn't exist (could not find package table_calender at https://pub.dartlang.org), version solving failed.
pub get failed (server unavailable) -- attempting retry 1 in 1 second...
Because infixedu depends on table_calender any which doesn't exist (could not find package table_calender at https://pub.dartlang.org), version solving failed.
pub get failed (server unavailable) -- attempting retry 2 in 2 seconds...
Because infixedu depends on table_calender any which doesn't exist (could not find package table_calender at https://pub.dartlang.org), version solving failed.
pub get failed (server unavailable) -- attempting retry 3 in 4 seconds...
`
The package table_calender is removed from the https://pub.dev.
It could be any reason why the author decided to pull the package, but That's the reason why your flutter pub get is failing.
Also if you are from Bangladesh, I see a lot of GitHub issues raised on the same topic. The solution is to use VPN apparently.

Issue with Firebase Function Integration

I have a issue with Firebase Function Integration, when I type :E:\APPS\Main Code\Android Code\app\GameRoom>firebase login
This is what I get:
? Allow Firebase to collect anonymous CLI usage and error reporting information? Yes
Visit this URL on any device to log in: https://accounts.google.com/o/oauth2/auth?client_id=563584335885-fgrh(...) Waiting for authentication…
Error: An unexpected error has occurred.
on debug debug Error: spawn cmd ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19) at onErrorNT (internal/child_process.js:456:16) at processTicksAndRejections (internal/process/task_queues.js:77:11)
I try with firebase login—no-localhost, but the same thing ,dosen’t work
If I click on the link I DON`T receive the message : Woohoo!
Firebase CLI Login Successful
You are logged in to the Firebase Command-Line interface. You can immediately close this window and continue using the CLI.
Thank you
If you're on windows then try running a separate cmd as admin and then use firebase login

bundling failed: Error and 404 when running React-Native project

I have a React-Native application which I'm running with npm start -- --reset-cache. Then I run react-native run-android.
However, I'm getting this issue in the console of the npm server:
Bundling `index.js` [development, non-minified] 0.0% (0/1), failed.
error: bundling failed: Error
at DependencyGraph._getAbsolutePath (/myProjectPath/node_modules/metro-bundler/src/node-haste/DependencyGraph.js:305:11)
at DependencyGraph.getDependencies (/myProjectPath/node_modules/metro-bundler/src/node-haste/DependencyGraph.js:283:4236)
at Resolver.getDependencies (/myProjectPath/node_modules/metro-bundler/src/Resolver/index.js:129:5)
at /myProjectPath/node_modules/metro-bundler/src/Bundler/index.js:642:39
at Generator.next (<anonymous>)
at step (/myProjectPath/node_modules/metro-bundler/src/Bundler/index.js:13:1336)
at /myProjectPath/node_modules/metro-bundler/src/Bundler/index.js:13:1496
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
And then, in the Android emulator, I'm getting:
The development server returned response error code: 404
URL: http//10.0.2.2:8081/index.bundle?platform=android&dev=true&minify=false
Body:
{"message": "Cannot find entry file index.js in any of the roots"
This confuses me. Why is it looking for index.js instead of index.android.js, since I am on an Android emulator?
Any idea about how I can fix this issue?
After version 0.49.1 index.android.js and index.ios.js files were merged into one file.
https://github.com/facebook/react-native/issues/16208
I understand that you will have to upgrade the applications in the old version.I guess this transition will be difficult.

The development server returned response error code :500

I have just created a React Native application in Webstorm , but when i run it, it shows this error :
The development server returned response error code: 500
URL: http://10.0.3.2:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false
Body:
{"message":"TransformError: F:\\MyApps\\CatalogueApp\\index.android.js: Unexpected token ) (While processing preset: \"F:\\\\MyApps\\\\CatalogueApp\\\\node_modules\\\\babel-preset-react-native\\\\index.js\")","type":"TransformError","lineNumber":0,"description":"","errors":[{"description":"","lineNumber":0}]}
processBundleResult
BundleDownloader.java:170
access$100
BundleDownloader.java:39
onResponse
BundleDownloader.java:139
execute
RealCall.java:135
run
NamedRunnable.java:32
runWorker
ThreadPoolExecutor.java:1113
run
ThreadPoolExecutor.java:588
run
Thread.java:818
Why ?
Below is the image :
This is what i did in the command prompt It helped me.
npm uninstall babel-preset-react-native
npm install babel-preset-react-native#2.1.0
It means the new version of babel-preset-react-native library and there is an unsupported trailing commas on that new version.
I had this problem. It resolved by correcting the code. Take a look at the node window that has opened when you ran "react-native run-android", It's reporting where's the problem, for example it reports:
Unexpected token (27:6)
and then it reports a part of your code that is making the error. Open up the App.js file, review the code part that has made the problem and correct it.
Take a look at the below picture and pay attention to the yellow part.

Android: Handle App Link Verification failure at install time

I added app link feature with autoVerify set for my app following link
On testing the app, it worked in the begining. Then after reinstalling the build, not working.
On debugging what I found is the response time for my .well-known/assetlinks.json file is > 1sec.
which gives timeout error on test-url https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://example.com&relation=delegate_permission/common.handle_all_urls
{
"maxAge": "599.999999353s",
"debugString": "********************* ERRORS *********************\n* Error: deadline_exceeded: Timeout occurred while fetching Web statements from https://example.com./.well-known/assetlinks.json (which is equivalent to 'https://example.com/.well-known/assetlinks.json') using download from the web (ID 1).\n********************* INFO MESSAGES *********************\n* Info: No statements were found that match your query\n"
}
Looks like because of this timeout, verification is failing.
I would like to know whether app/system retry verification at any point later if verification failed on install (may be because of connection issue or temporary website down)?
Unfortunately Android M does not automatically reattempt verification if it fails due to timeout or connectivity issues. As you found in this guide the next attempt will occur on app update or re-install.

Categories

Resources