I have been successfully using classic build system, and OTA also working as expected.
eas cli : 1.2.0,
expo sdk : 45
workflow : managed
As expo build is going to stop from jan-2023, I thought to switch to eas,
I am able to successfully build with eas build,
but with next eas build version, OTA is not happening at client side
eas update also completes publishing successfully, but it does not OTA update client side either.
Kindly help to resolve the issue, and also let me know that.
eas update works with managed workflow ?
thanks
Related
I am trying to run a react native project on the simulator using expo go. However, I am getting errors.
What I tried:
package.json has the version 34.0.0 for expo.
When running this on the simulator I get the below issue.
I then try to upgrade my expo, but getting an error there too.
At present we're migrating our build infrastructure from expo with turtle to use EAS local builds. One of the issues we had with turtle is the need for setting up an external web host or use expo publish before you run turtle.
Does EAS local build still require the expo publish? step before calling the eas build --local?
I am beginner at using AWS .so i want to ask some questions about CodePipeline.
so all i know about CodePipeline ,that i can connect it to github repo to let my app updated automatically ... then when i am doing the steps something called build provider appeared (its optional) .. and when i skip it it says "Your pipeline will not include a build stage"
so why do i have to do a build provider when my project compiled and build successfully locally on my PC ,i know its an optional step ,so can i know what it do exaclty ?
When you are automating your code deployment process you cannot build your code locally as its a manual process.
To Automate the process code-pipeline has a build provider which can build your code as n when required. So, that you don't need to checkout the code locally and build before deploying.
I had no idea Expo did this.. But I created a small office application and working on an update. While working on the update, I did
expo publish
So that the team I'm working with could use Expo and see the route I'm going. And it updated the production app throughout the company.
in my App.json file
"updates": {
"enabled": false,
"checkAutomatically": "ON_LOAD",
"fallbackToCacheTimeout": 0
},
I want to still be able to publish the app, without it updating the production app.
how do I do that when I publish?
Check out Expo release channels.
When you build your standalone apps to iOS or Android it binds that build to whatever release channel was specified. It is set to default channel by default.
You can build your apps to a specific channel by running:
expo build:ios --release-channel <your-channel>
expo build:android --release-channel <your-channel>
Then, when you want to publish to that release channel you do so by running:
expo publish --release-channel <your-channel>
I'm working on a project that I haven't touched in about 4 months. Before everything on the deploy was working fine, but now I'm getting an error when trying to deploy an update.
Failed to pull Docker image amazon/aws-eb-python:3.4.2-onbuild-3.5.1: Pulling repository amazon/aws-eb-python time="2016-01-17T01:40:45Z" level="fatal" msg="Could not reach any registry endpoint" . Check snapshot logs for details. Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/03build.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
In the eb-activity log, it further states [CMD-AppDeploy/AppDeployStage0/AppDeployPreHook/03build.sh] : Activity execution failed, because: Pulling repository amazon/aws-eb-python before repeating what was shown in the UI.
The original was using a Preconfigured Docker 64bit Debian jessie v1.3.1 running Python 3.4. I've tried upgrading to the latest, which is version 2.0.6, but it never completes (don't need to get into specifics of that error, separate issue and I'd like to stay on 1.3.1 if possible). I've also tried upgrading to the latest 1.x but it has the same result of upgrading to 2.0.6.
Any ideas, or anything else I should be looking for clues?
Docker Hub has deprecated pulls from Docker clients on 1.5 and earlier. Make sure that your docker client version is at least above 1.5. See https://blog.docker.com/2015/10/docker-hub-deprecation-1-5/ for more information.