I tried to update my AWSSDK for windows with one released 1 DEC to test a new Lambda with C#.
But I got error message like this.
Product: AWS Tools for Windows -- Error 1722.
There is a problem with this Windows Installer package.
A program run as part of the setup did not finish as expected.
Contact your support personnel or package vendor.
Thanks for the report, and we apologize for the inconvenience caused.
As noted by others, for this install we changed how we install the toolkit and for some users this is causing install fails that we have not managed yet to reproduce in-house and are still trying to find root cause for.
Feel free to post your install log here (if you have it), or on the AWS forum thread posted above where we are tracking the problem and gathering data from affected users.
What version(s) of Visual Studio do you have installed, and was this an upgrade install from a previous version?
We released version 1.11.1.4 of the AWS Toolkit for Visual Studio to resolve the installation problems. You can download the latest version from https://aws.amazon.com/visualstudio/
Related
I was working on my React Native project with AWS Amplify, everything went well
One day, I tried the AWS Cognito authentification feature I added few weeks ago, and it is not working anymore and I dont understand why. I searched for the error log all over the internet but nothing found.
Please help
When I call the Auth.signIn() method, I get the following error:
Expo managed workflow support for amazon-cognito-identity-js is only available in SDK 39 and higher.
Problem solved, I went through many problem during installations but what made it for me was to install the latest version of expo (expo upgrade) (SDK 39 at least) and update all my package using a npm library:
npm install -g npm-check-updates
ncu
ncu -u
I'm trying to set up MinGW. I have downloaded the latest installer, which installs mingw-get but this utility fails to fetch the packages and gives the following kind of messages:
mingw-get: * ERROR * Get package: http://prdownloads.sourceforge.net/mingw/gcc-4.5.2-1-mingw32-lic.tar.lzma?download: download failed
There is no firewall running. Anyone had the same problem?
Thanks to all.
Try with "Administrator rights" . It helped me.
This problem has happened to me too and was due to - I guess - temporary problems to either the network or sourgeforge itself. I suggest retrying after a while.
This problem comes from the network. I can't download it by using my fiber broadband microtalk communication bit it still downloading by using my jio mobile network.
Try installing it from osdn.net
Here's the link: https://osdn.net/projects/mingw/releases/
It's same as sourceforge but was able to connect and download
worked for me and my friends!
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 have been trying to install the Azure Functions and Web Jobs extension, however installation fails. Looking through the error log it appears that the piece that isn't working is this:
Install Error : System.InvalidOperationException: Installation of Azure Functions and Web Jobs Tools failed. To install this extension please install at least one of the following components: Microsoft Azure WebJobs Tools
I think that the problem is that it is looking for itself with the wrong name (Microsoft Azure WebJobs Tools instead of Microsoft Azure Web Jobs Tools). Is there any way to fix this?
Just had the same problem and the error was not very helpful :( Fixed it by installing the Azure Development "workload" from the Visual Studio Installer. After running the installer, you can choose to modify the installation and add this. It will actually come with the extension you're trying to install, oddly enough, but it will not be the latest version of it.
Here is an image which I hope helps:
I get Package restore failed. Rolling back package changes for 'ConsoleApp1' while installing a new package. In particular I am trying to install the dropbox API, but I tried several other packages and get the same result.
I install by right clicking on the project and choosing Manage nuGet Packages... Then I select the package and click Install.
The NuGet is able to connect with the NuGet server as the package seems to download. The download information flashes on the screen pretty quick so I captured it with screen recording software to see if there were error messages. There were none.
I updated visual studio 2017 to latest patch level. My windows 10 machine is also at the latest level.
The project I am trying to install into is a freshly created Console App(.Net Core).
Here are the other questions I looked at:
Package restore failed. Rolling back package changes
does not have any responses because it is not a well developed question.
package restore failed rolling back package change for ' myproject' in vs 2017 .net mvc core project
Yet another poorly worded question with no viable answers.
Package restore failed. Rolling back package changes for 'myproject' in vs 2017 in MVC Core
That one is trying to update packages, not install new.
Nuget - Package restore failed. Rolling back package changes for 'WebApplication1'. 0
Seems to be for a custom package.
I am new to using Visual Studio.
To expand on #Michael Potter's answer, create a Console App (.NET Framework), NOT Console App (.NET Core).
The problem was that I am using Console App(.Net Core) Core is not compatible with Dropbox API.
I figured that out by opening NuGet Package Manager -> Package Manager Console and running Install-Package Dropbox-Api.
Then the error message about compatibility was on the screen plain to see.
To solve the problem I am switching to Console App (.Net Framework).
bring the version of the solution package to 1.1.3enter image description here