Expo android api target level 28 change to 29 - react-native

I am using expo version 37. I built an standalone app to be uploaded on play store. When I tried uploading the apk file. I got the error:
expo your app currently targets api level 28 and must target at least api level 29
How can I solve this problem?

Run expo upgrade and then re-build your Android standalone app using expo build:android -t apk

Looks like the Expo team is aware of the issue as stated here and looking to fix this week.

you must upgrade to expo SDK38 , and it works now !
If your SDK is 37.
follow this upgrade expo

Related

After Expo eas update app is crashing for managed workflow

I updated my expo version from 45 to 47 and created a build using eas and tested it on the device, it's working fine.
But the app crashes(iOS and Android both) when doing OTA using eas update.Also not getting any error while releasing via OTA.
Tried this Github solution but didn't work

Building expo app is not updating the app in store

I used to run expo build:android (or ios) to build and publish my react-native application.
The app in the app store automatically updated doing this.
Since I updated my expo version to 38.0.8 it doesn't seem to be working anymore?
Does anyone know what's the problem here?
Generally you have to run
expo build:ios(or android)
to generate an expo build, and then run
expo upload:ios(or android)
to upload to the App Store or Google Play Store

Expo: Ejecting to a bare project is only available for SDK 34 and higher

I have a Expo project that I have to eject, due to some native libraries that I must implement. But when i run Expo eject and chose Bare: I'd like a bare React Native project, the console pops up this error:
Ejecting to a bare project is only available for SDK 34 and higher
By searching a bit I understood that expo sdkVersion 34.0.0 is not available yet right? If not, How can I update to it?
Thank you!
I met the same problem as you, I found a link at Expo forum: https://forums.expo.io/t/expo-ejecting-to-a-bare-project-is-only-available-for-sdk-34-and-higher/25528 suggesting to downgrade expo-cli version with
npm i -g expo-cli#2.21.2
if you want to eject to plain react native.
I did so and it works, they said that SDK 34 will be released soon.

Can't run the .apk that generated by Expo

I have built an android app using expo build:android for a react native project. And then I can't ran the .apk on my 2 android phones. Error message App not installed was shown after ran the .apk on my phones.
I tried to rollback to older versions of my code and I found that the .apk can ran after I used the old slug value in app.json
I installed the .apk at android emulator. Error message The APK failed to install.
Error: INSTALL_PARSE_FAILED_NO_CERTIFICATES: Package /data/app/vmdl1022936792.tmp/base.apk has no certificates at entry AndroidManifest.xml is shown.
Having no ideas why this happens. How I can use a new slug value and build a valid .apk via Expo?
I feel code signing is the problem, the app is not able to install on another android only for this reason.
Use this link
https://docs.expo.io/versions/latest/distribution/app-signing/
try using command
expo build:android --clear-credentials

Error 400 when build:android setting keystore manually

We have an app previously built on phonegap and now migrated to React Native/Expo. We are trying to build the android .apk using the keystore we had before and we get the following error:
I know that the problem is not with my .keystore, since through expo fetch:android:keystore I’ve got the keystore generated by EXPO and it gives me the same error!
Using expo build:android works fine, but I can’t deploy since the fingerprints doesn’t match with the app I have already published.
Any ideas?
Thanks!
There was an issue with expo-cli 2.7.1 and it's fixed on 2.7.2. So just needed to update my cli version!