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
Related
today i opened termux for installing node.js on my phone (because i need npm), but it doesn't work, i runned pkg install nodejs but it gave me the error: unable to locate package nodejs.
I checked my connection and i'm connected to wi-fi with a really good speed, so i tried to install another common package to see if the problem was only for the node.js package or in the whole app,
i tried to install git and it gave me the same error.
So i started searching in forums: stackoverflow, github forum, termux wiki, etc...
I tried everything, apt update, pkg update, apt upgrade, pkg upgrade, etc...
Those gave me the error: the error
So, i don't know what to try anymore, please give me an answer, have a nice day.
This error is common one. You should change repository mirror for your termux packages.
Here is the instruction from the official Termux github page.
To select multiple repositories press space. To select new mirror for repositories use space and then enter.
Termux can be used for hacking and many other suspicious things which is definitely against playstore policies. So you just need to uninstall termux playstore version and download termux from F-Droid. That is actual termux not the play store one. You should not face any error in that termux.
Nothing else worked, neither running some command nor changing repo. The only thing which works is downloading termux from F droid
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 am using Loopback 4 to create a REST-ful API. I'm a mobile developer by trade so typescript et al is all pretty new to me, so please be kind ;)
I created the app using CLI v1.21.4, and saw a message to say that an update is available. I therefore updated my global installation of the CLI. But then when I try and run one of the commands such as lb4 model I see the message:
The project was originally generated by #loopback/cli#1.21.4.
The following dependencies are incompatible with #loopback/cli#1.23.1:
typescript: ~3.5.3 (cli ~3.6.3)
#loopback/authentication: ^2.2.2 (cli ^3.1.1)
I would of course like to take advantage of these newer modules, but I am unsure how to update my app scaffolding and dependencies. Could anyone offer some advice please?
Please check out https://github.com/strongloop/loopback-next/issues/3608:
During lb4 app, we add the cli version to .yo.rc.json, such as:
{
"#loopback/cli": {
"version": "1.21.4"
}
}
lb4 -v lists compatible modules that are released with the cli.
lb4 commands check if the project has incompatible versions with the current cli and prompts users to force or exit.
I would of course like to take advantage of these newer modules, but I am unsure how to update my app scaffolding and dependencies.
The process for updating dependencies is not specific to LoopBack. If you are using npm, then simply run npm update.
Please note that TypeScript often introduces backwards-incompatible changes in semver-minor releases, 3.6 brought few of them. Be prepared to manually fix few compilation errors after the upgrade.
I think that npm update is not going to jump from v2 to v3 for #loopback/authentication, you have to request that upgrade explicitly:
$ npm install #loopback/authentication#latest
There is now a supported update procedure, which is documented here:
https://loopback.io/doc/en/lb4/Update-generator.html
It seems to be simply:
# Ensure you have the latest version of the CLI tool
npm install -g #loopback/cli
# Then ask the tool to check which packages should be upgraded
lb4 update
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/
I'm trying to download the facebook/php-sdk-v4 repository into my project, running the "php composer.phar update" command.
I recently added this to the require section of my composer.json file:
"facebook/php-sdk-v4": "4.0.*",
Upon running the update command, I am given the following error:
---> Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package facebook/php-sdk-v4 1.0.0 could not be found.
It seems that I have set it up exactly according to the Facebook Graph API instructions as listed on this page:
https://developers.facebook.com/docs/php/gettingstarted/4.0.0
But... It's still unable to find the repository.
Does anybody know the name of the Facebook SDK 4.0 repository or see any reason why this process I am following isn't working?
Thanks for listening!