Using fastlane in the console, it tells me, that there is an update available and I should update using the App.
fastlane 2.27.0 is available. You are on 2.25.0.
It is recommended to use the latest version.
Please update using the Fabric app. Launch the app and navigate to the
fastlane tab to get the most recent version..
But I don't see any possibility to update.
Mike from Fabric here. If you don't see the update button present, try quitting and relaunching Fabric.app to force a check for an update. Once that's done, you should see the option to update below the Fastlane logo.
Related
I want to ask about a certain codepush scenario.
If my Codepush enabled react native App does a rollback while installing a new update due to unknown reason (failed install etc. ), then will it try to re-sync and try to install the latest codepush update again?
I looked in the Docs for this, but couldn't find anything solid and it is very difficult to re-produce this to test it manually.
When I start my project using command expo start , Expo is starting the Metro bundler but not opening the developer tool. Also developer tool option is not available in commands menu.
I suppose there should be command option : 'd' which will launch the developer tool on the localhost:19002 but it's not coming for me.
Using expo cli version 5.4.4
Developer tools removal
Since the release of expo-cli#6.0.0 the expo team has decided to discontinue the Web UI they had put in place. You can find more details about this in this blog post.
All of the actions that could be done within the Web UI can be done within the command line interface. For example, one used to be able to change connection mode directly within the UI :
Now to start expo in --tunnel mode you would have to have ngrok installed on the new expo version npm i -g #expo/ngrok and to run npx expo start --tunnel. Details on the CLI can be found in the docs here.
Accessing the Developer tools anyway
If you still wish to use the developer tools web UI, there are two options :
Use an older version of the expo sdk (~44.0), to do so you could use expo-cli#5.0.2 which is linked to that sdk. However, it is not recommended to stay on older versions which will be discarded at some point.
Use your own Web UI. Here is the source code from expo's original Web UI which you can use a base. There are likely over repos out there which fit this purpose.
If you're using a library such as react-navigation or anything (or itself) the relies on reanimated you won't be able to use remote debugging. https://docs.expo.dev/versions/latest/sdk/reanimated/
After changing the expo sdk version from 45.0.4 to 44.0.6, I am able to see the Developer tools running on http://localhost:19002.
I released one apk from PlayStore. Now I want some updates couple of screens. This changes required to use some new libraries. With this new library I'll achieved my requirements. Now I want to update remotely with manual release, using react-native-code-push. Is this possible? I know the appcenter only updates bundle file. But I didn't made any changes in native folder.If there anyway?
If the new npm package you are using contains native code then no, those changes will not go through using code-push. Only JS changes are going to go through.
You can create a local build with some build version that you'll never use and give a code push to that particular version and test it.
I have two standalone APP building by Expo, one for iOS which push to testflight so internal iOS users can test it, another is just an APK let Android users can download and test.
Like Expo document said, I publish code to release-channel 'staging' then build these two APP by release channel staging, all are good and my users can start testing with testflight/APK.
But when I modify code and publish again, no OTA update happen, and in my Expo dashboard, the version code is just the previous one (I've also updated version/android.versionCode/ios.buildNumber in app.json).
What should I do to make the OTA update works? If need any other information please let me know, any suggestion is appreciated!!
I developed an app with React Native and distributed it with Expo. I published the final version into Google Play and Apple Store.
Some time later I discovered in Expo's docs on Publishing that expo publish allows you to create an OTA ("over the air") update that is built into Expo and updates the app automatically, according to this answer:
The standalone app knows to look for updates at your app's published url.
This I tested and worked very well.
However, now I see that people downloading the app from the stores (that is, either Google Play or Apple Store) apparently get the initial version of the app, not the updated one.
What is the exact workflow for the OTA updates? Do they go and "replace" the existing version in Google Play and Apple Store the first time they open it? Or do they need to open it over again to get the update?
And what exactly triggers the update of the app?
We've been having similar problems. I can see two things which might be causing this in your case:
Check in app.json if updates.fallbackToCacheTimeout is set. If it's set, that's how long expo will try to download the latest update before showing the last downloaded version (which will be the initial version after initial download).
If you have a large update, expo will try downloading the update for 30s before showing the last version of your app.
Check here for more info: https://docs.expo.io/versions/latest/guides/configuring-ota-updates/
OTA updates do not replace the version downloaded from the app store, they are stored first in the device's cache before being run on app start after download. Source https://docs.expo.io/versions/latest/sdk/updates/
Update downloads are automatically triggered on app start, then, depending on the settings it will either wait (as long as updates.fallbackToCacheTimeout allows) before showing the app, or show it immediately.
You can force the app to run the latest update (if you have one waiting) by just force quitting the app, then restarting.
Hope this helps!