I have build an app with expo. Let's say version 1.0.10
This app is available on test flight and I can install and check the functionality.
Now, if I find some issue, I use expo publish --release-channel production to fix the same.
Next time when I open my app, I receive the latest updates and issue is fixed.
But the problem is, if I delete the app, and install it again from the test flight, it still has the old version of code i.e. from 1.0.10. To see the latest updates, I have to kill the app and open it again. Is there a way to handle updates correctly? All the new installs should get the latest updates.
I tried multiple updates over version 1.0.10. But the latest updates are not available on new installs. I always have to kill the app and open it again to get the latest, which is not what i want.
Should I include a step to check if updates are available, and if yes, get the latest updates. Build this with version 1.0.11 and try expo publish and see new installs has the latests updates?
Related
When trying to create a custom ElasticBeanstalk platform that uses Python3.10.5, I keep running across this error:
[2022-07-01T05:50:06.466Z] INFO [5419] - [CMD-PackerBuild/PackerBuild/PackerBuildHook/build.rb] : Activity execution failed, because: Version 2 of the Ruby SDK will enter maintenance mode as of November 20, 2020. To continue receiving service updates and new features, please upgrade to Version 3. More information can be found here: https://aws.amazon.com/blogs/developer/deprecation-schedule-for-aws-sdk-for-ruby-v2/
'packer build' failed, the build log has been saved to '/var/log/packer-builder/Python3.10_Ubuntu:1.0.8-builder.log' (ElasticBeanstalk::ExternalInvocationError)
caused by: Version 2 of the Ruby SDK will enter maintenance mode as of November 20, 2020. To continue receiving service updates and new features, please upgrade to Version 3. More information can be found here: https://aws.amazon.com/blogs/developer/deprecation-schedule-for-aws-sdk-for-ruby-v2/
'packer build' failed, the build log has been saved to '/var/log/packer-builder/Python3.10_Ubuntu:1.0.8-builder.log' (Executor::NonZeroExitStatus)
I'm not sure how to get around it, as none of my actual code for this uses ruby at all.
I have tried to SSH into the packer build box and run gem install aws-sdk to get the latest version, however it eventually ends up hanging and never completes.
I'm really unsure of what to do at this point. Any advice?
Update: Was finally able to get a gem install aws-sdk -V to finish after changing the version to ruby2.4, however the problem above still persists.
after build expo, i released at play store.
After this i installed dependency to add useful function.
("react-native-draggable-flatlist")
is it possible to publish?
If this is not possible, I have to remake apk.
oh, and if i built expo(making apk file), can i publish?
I didn't take any action before build.
yes you can after building expo released apk
If you make any of the following changes in app.json, you will need to re-build the binaries for your app for the change to take effect: Increment the Expo SDK Version Change anything under the ios, android, or notification keys Change your app splash Change your app icon Change your app name Change your app owner Change your app scheme List item Heading
see the doc here
When trying to build my Expo project, using expo build:ios, I get the following error:
Unsupported SDK version: our app builders don't have support for
33.0.0 version yet. Submitting the app to the Apple App Store may result in an unexpected behaviour Unsupported SDK version
What is causing this error and how can I fix it?
What causes this error?
This error is caused by the fact that as of March 31st 2020 the Expo client no longer supports Expo SDK 33. From the Expo release blog we see the following:
Dropping SDK 33 from the Expo client
We routinely drop SDK versions
that have low usage in order to reduce the number of versions that we
need to support. This release sees the end of life for SDK 33. As
usual, your standalone apps built with SDK 33 will continue to work;
however, SDK 33 projects will no longer work within the latest version
of the Expo client. If you want to re-run expo build, then you’ll need
to upgrade from SDK 33, preferably to SDK 37 so you won’t need to
update again for a while (and also because each Expo version is better
than the last!).
How do I fix this?
To fix this error you need to upgrade the SDK that that your Expo project is using. Ideally you should upgrade to the latest version. In this case Expo SDK 37 as that will give you the longest amount of time until you have to upgrade again.
To upgrade the SDK. Expo has a fantastic resource detailing what you have to do here. Each blog post give steps on how to upgrade.
Here are the basic steps on how to upgrade:
Run expo upgrade in your project directory (requires the latest version of expo-cli, you can update with npm i -g expo-cli).
Make sure to check the changelog for other breaking changes!
Update the Expo app on your phones from the App Store / Google Play. expo-cli will automatically update your apps in simulators if you delete the existing apps, or you can run expo client:install:ios and expo client:install:android.
If you built a standalone app previously, remember that you will need to create a new build in order to update the SDK version. Run expo build:ios and/or expo build:android when you are ready to do a new build for submission to stores.
Make sure you check the changelogs
As you are upgrading from SDK 33 you will need to look at the different changelogs that exist for upgrading from 33 to 34, 34 to 35, 35 to 36, and finally 36 to 37. This is because there could be something that occurred in one of those updates that may break something in your app.
How can I avoid this problem in the future?
Simply, make sure that you keep your apps up-to-date. Upgrading many versions of Expo and/or React-Native can be cumbersome as features are added and removed with each release. The easiest way to stay on top of it is to upgrade frequently, I find that by setting aside a coupe of days a month to check the dependencies etc that I am using are up-to-date means that I do not have to massive upgrades. It also means I am in a better place to know what it going to cause a problem and I have more time to fix it.
tl;dr
Update your Expo SDK version to the latest release.
Incompatible version of SDK..
For me, it worked after updating the Expo app from Google play store..
After I download the Google Cloud SDK install package, I trigger the install and click all the Next buttons in the wizard to accept all of the default installation options. However, this process errors out before completion. I've attempted this install process 3 times and it errors out each time.
Any idea what the issue might be or how to debug?
I want to run an API call after every 5 mins in the app. I want to generate a notification whenever new data is added to the database through the API.So to check this I need to run the task in background to make it a real time application.
How can I achieve this task in Django?
I am facing multiple errors while using django background_tasks so I don't want to use it. Celery is not compatible with windows. Is there any other option whose tutorial is available also
As you mentioned in your another question here ,
you previously have installed django-background-task instead of django-background-tasks [notice the difference between task and tasks]. So you have got ImportError: cannot import name 'background' from 'background_task'.
Later you installed the proper one i.e django-background-tasks and then you uninstalled django-background-task which also uninstalled some of the dependencies of django-background-tasks.
SOLUTION: Uninstall both packages first. Then pip install django-background-tasks