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..
I´m using Windows 10 and following the "Getting started" tutorial, but after creation of user I can´t create the credential for him.
the command line:
eg credentials create -c bob -t key-auth -q
the result:
Configuring yargs through package.json is deprecated and will be removed in the next major release, please use the JS API instead.
Configuring yargs through package.json is deprecated and will be removed in the next major release, please use the JS API instead.
Configuring yargs through package.json is deprecated and will be removed in the next major release, please use the JS API instead.
then I must press Control+C to stop the process.
unfortunately yes, we have a problem with yargs on Windows which is actually tracked in our GitHub repository: https://github.com/ExpressGateway/express-gateway/issues/889
My idea would be to replace yargs with oclif or something modern, but I haven't been able to work on it yet.
Also, I do not have a Windows machine so it is kind of difficult to test it out properly.
I am having an issue with the SSDT installation for VS2017.
I have ran the installer three times, once basic, once following VS update and the last following some minor windows updates.
All 3 times the logs stumble at the same point, anyone know what this .exe it is trying to run is (I am running the installer with Admin...). I read somewhere for a similar error that it might be the SDK but I am able to run this locally, any nice workarounds to having this installed out there?
[29BC:A138][2017-09-26T09:28:00]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 4
[1EC4:6DB0][2017-09-26T09:28:00]e000: Error 0x800703e9: Process returned error: 0x3e9
[1EC4:6DB0][2017-09-26T09:28:00]e000: Error 0x800703e9: Failed to execute EXE package.
[29BC:A138][2017-09-26T09:28:00]e000: Error 0x800703e9: Failed to configure per-machine EXE package.
[29BC:A138][2017-09-26T09:28:00]i000: MainViewModel.OnPackageAction: Install Completed for package SQL Server Analysis Services (id: Microsoft.DataTools.AnalysisServices)
[29BC:A138][2017-09-26T09:28:00]i319: Applied execute package: Microsoft.DataTools.AnalysisServices, result: 0x800703e9, restart: None
[29BC:A138][2017-09-26T09:28:00]e000: Error 0x800703e9: Failed to execute EXE package.
[1EC4:6DB0][2017-09-26T09:28:00]i351: Removing cached package: Microsoft.DataTools.AnalysisServices, from path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\
[29BC:A138][2017-09-26T09:28:00]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100
[1EC4:6DB0][2017-09-26T09:28:00]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5d5d6235-5c8c-4377-9a75-1b6368850657}, resume: None, restart: None, disable resume: No
[1EC4:6DB0][2017-09-26T09:28:00]i330: Removed bundle dependency provider: {5d5d6235-5c8c-4377-9a75-1b6368850657}
[1EC4:6DB0][2017-09-26T09:28:00]i352: Removing cached bundle: {5d5d6235-5c8c-4377-9a75-1b6368850657}, from path: C:\ProgramData\Package Cache\{5d5d6235-5c8c-4377-9a75-1b6368850657}\
[1EC4:6DB0][2017-09-26T09:28:00]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5d5d6235-5c8c-4377-9a75-1b6368850657}, resume: None, restart initiated: No, disable resume: No
[29BC:A138][2017-09-26T09:28:00]e000: MainViewModel.OnBundleAction: Bundle action failed: Recursion too deep; the stack overflowed (0x800703E9)
[29BC:A138][2017-09-26T09:28:00]i399: Apply complete, result: 0x800703e9, restart: None, ba requested restart: No
[29BC:6724][2017-09-26T09:28:04]i000: MainViewModel.OpenUrl: Opening url: C:\Users\RTOMPS~1\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20170926092556.log
The answer from Nick is very helpful, but I still failed at SSDT-Setup-ENU.exe /repair with the same error Error 0x800703e9: Failed to execute EXE package..
Then I tried it with a very straightforward way: (Disable UserAccountControl first)
copy SSDT-Setup-ENU.exe to c:\temp and execute SSDT-Setup-ENU.exe /layout to download a local copy of the bundle.
open C:\temp\redist and double click NDP461-KB3102438-Web.exe
open C:\temp\payload and double click vsta_setup.exe
repeat to install others...
This is the most likely link I came to when I got the same message in my log:
Applying execute package: Microsoft.DataTools.AnalysisServices, action: Install, path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe" /q /admin /instanceIds:"fc3f0e2c" /logFile:"C:\Users\a_nzchuk\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20171205113839_002_Microsoft.DataTools.AnalysisServices.log" "payload\Microsoft.DataTools.AnalysisServices.vsix"'
MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 17
MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 17
...........
...
Error 0x800707d3: Process returned error: 0x7d3
Error 0x800707d3: Failed to execute EXE package.
Error 0x800707d3: Failed to configure per-machine EXE package.
MainViewModel.OnPackageAction: Install Completed for package SQL Server Analysis Services (id: Microsoft.DataTools.AnalysisServices)
Applied execute package: Microsoft.DataTools.AnalysisServices, result: 0x800707d3, restart: None
So I'll document my findings here.
In my start menu I had Visual Studio 2017 (SSDT). It ran OK but didn't have any BI projects available
This is what I did from an Administrator elevated command prompt:
Copied SSDT-Setup-ENU.exe into C:\temp (rather than a user specific download folder which the admin user may not have access to)
Ran SSDT-Setup-ENU.exe /layout to pre-download support and redist files (this was after a required restart)
Ran SSDT-Setup-ENU.exe /repair to try and repair the install. It gave me a button Repair that I clicked.
Ran SSDT-Setup-ENU.exe /repair again. Selected Modify. Noted that only SQL Server Database was ticked, but none of the others (SSAS, SSIS, SSRS)
Ticked SQL Server Analysis Services and pressed Modify. It proceeded to do it. Got stuck at 50% for a few minutes but eventually worked
Repeated for SQL Server Reporting Services and SQL Server Integration Services
After this, when I reran VS2017, it had the BI projects and allowed me to create a 1400 SSAS solution
Previous failed installations left VS2017 recognising that the installation was present in Visual Studio Installer. I removed the installation, restarted and the re-install was successful...
For SSDT for VS2018, Version 15.5.2
same failed at execute exe. only do
1. SSDT-Setup-ENU.exe /layout
2. SSDT-Setup-ENU.exe /repair (tick SSAS/SSRS/SSIS based on your requirement)
and this already works. I think MS also do some job for this.
EDIT: This might not be relevant any more since SSDT 15.8.2 is now out.
In my case, I was on VS 2017 15.7.2 and I can't complete the installation in SSDT 15.6. What I did was to install SSDT 2017 15.7.0 and it worked.
Make sure to uninstall previous SSDT installations via the VS installer or Control Panel also the Microsoft Reporting Services Projects and Microsoft Aanalysis Services Projects extensions first if you have them before launching the installer.
Edit: I think my Python issue is a subset of Jeff Leach's comment about repairing Visual Studio. So, I would probably look at any Visual Studio errors you had while installing and try and fix them before trying to install SSDT. For the time being I would NOT update Visual Studio or its installer to the newest versions (15.7 and 1.16) because of known bugs with SSDT 2017. They are working on a fix that will be out with 15.7.2 but it's not out yet.
Info for the edit:
https://developercommunity.visualstudio.com/content/problem/246732/ssdt-1560-installer-the-configuration-registry-key.html
I found that Daniel's method worked, but I had to install Python manually to be successful.
After successfully installing the .msis in the payload directory I tried to install the Analysis Services VSIX and I wasn't successful because the installer couldn't install Python 3.6.3. I found the page at the bottom and did the following to successfully install the Analysis, Integration, and Reporting VSIXs.
Check error logs and find what version of Python is the problem.
Manually download and install the proper Python version (my logs said 3.6.3). The name of the executable was python-3.6.3-amd64.exe and I got it from https://www.python.org/ftp/python/3.6.3/python-3.6.3-amd64.exe
Uninstall SSDT extensions from within Visual Studio. I uninstalled all of my previously unsuccessful VSIXs.
Manually install VSIXs. This worked out for me and I am able to use all of the SSDT functionality!
Just to do control testing, I installed Reporting Services with the /repair option and was successful. I think the main issue was the Python error. I think if I would've had Python installed everything would've gone smoothly. This is very frustrating because I got this same Python "error" when first installing Visual Studio 2017 (15.6.7)...expect the "error" was just a caution and didn't prevent me from using Visual Studio. But somehow it prevented the install of SSDT 2017.
I hope none of y'all have to go through this like I did today at work!
Info that helped solve this:
https://developercommunity.visualstudio.com/content/problem/98172/packageidcpython3exex64packageactiondownloadpackag-1.html
I had the same error 0x800703e9 installing SSDT with the SSRS option checked. After trying some of the previous good suggestions unsuccessfully, including using the /layout option to download the package locally, I found that the Visual Studio installer portion of the package needed a reboot to finish. After the reboot, I was able to run Microsoft.DataTools.ReportingServices.VSIX successfully.
I have a similar problem with different error code, but the same
"Failed to execute EXE package problem".
I tried all the solution above to no avail. But, after creating an installation layout out of SSDT-Setup-ENU.exe and then trying to execute vsta_setup.exe as suggested by Daniel. I get to the underlying error message, it's has something to do with Android NDK believe it or not, and since I'm from Syria, any change to these packages should be done through a VPN connection. So the solution was to run Visual Studio 2017 installation layout, remove all these ugly android packages "Android SDKs and NDKs and even the emulators, yes, a nuclear solution since I don't have a VPN connection", and then run SSDT-Setup-ENU.exe /repair. Everything worked just fine.
I hope this might save someone's time after it wasted mine.
My installation came also with a error. I tried the several things mentioned above, but it didn't help. So I was guessing that it could be the disk space of my VirtualBox VM. I made the C: drive bigger and that was the trick.
SSDT requiere:
Hard disk space: up to 130 GB of available space, depending on features installed; typical installations require 20-50 GB of free space.
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.
When you attempt to apply any hot fixes via the ColdFusion 10 Administrator you continuously get:
Error occurred while installing the update:
Failed Signature verification
You may have even validated the files and manually and placed them in the hf-updates directory at which point the CF10 admin page still shows the "Install" option, but again you receive the same error.
This error means you've forgotten to apply the ColdFusion 10 Mandatory Update which updates the certificate used to validate install packages.
From Adobe's website:
All ColdFusion updates are now signed with the new code signing
certificate because of a code signing certificate revocation. This
mandatory Update ensures that your current installation of ColdFusion
10 is updated with the new code signing certificate. This update is
also required for proper functioning of the auto update functionality
in ColdFusion 10. Adobe strongly recommends that you apply this
update.
Once the update has been installed (you can find the JAR install instructions here) the service will be restarted and you will be able to apply subsequent updates via the ColdFusion administrator.
Edit:
Run the command prompt as Administrator:
Navigate to your jar file, and run the following command to run jar file:
D:\>java -jar cf10_mdt_updt.jar
#UncleSol,
I also encountered the issue after having installed the mandatory update (cf10_mdt_updt.jar). After successfully applying the mandatory update, CF wanted to apply update 12 as the first update, which is where I encountered this issue, so I downloaded and manually installed Update 11 from this page:
https://helpx.adobe.com/coldfusion/kb/coldfusion-10-updates.html (installed in exactly the same manner as NotJustClarkKent's instructions)
After manually installing update 11, I was able to use the CF Updater to install the rest of my updates.
Hope that helps.