Updating JavaScript SDK v2.19.2 to latest version
"Action required: JavaScript SDK v2.19.2 is no longer supported Please update your application to the latest version".
Has anyone done this update before. Do I just click the "latest version" to update?
This means that one or more of your applications uses the LaunchDarkly JS client with an outdated version.
Most probably it looks something like that in your package.json:
"launchdarkly-js-client-sdk": "^2.18.3",
// or maybe:
"launchdarkly-react-client-sdk": "^2.18.0",
You should update the version to the latest, and then re-build and deploy your app the way you usually do so the new code is used.
Related
I have integrated the electron app with the auto-updater and published the electron app as well. I am able to receive the newer version pop-up and able to upgrade my electron app but when I relaunch the installed electron app the app shows the previous version information and asks to install the newer version again. Any suggestions?
I bumped across your question because I was having the same issue. I was using auto-updater with Quasar framework. Maybe this could help someone else.
Since nsis was configured by default to do the oneClick installations (with predefined rules), it was always installing my application somewhere in users/AppData folders, which I didn't even notice.
The thing I was running over and over again (after successfully auto-updating application) was actually installing the previous version all over again.
To circumvent this issue, I changed nsis configuration to allow users to select their own installation path.
nsis: {
oneClick: false,
allowToChangeInstallationDirectory: true
}
After this, app shortcut was appearing on desktop, which was always running the latest version.
I recently incrementally upgraded my Wagtail installation from 2.15.2 to 2.16.2, but the Wagtail version in the admin interface is still stuck in the old version. What can I do to fix this?
As #LB Ben Jonston suggested, in the end the problem was even though the Docker image was built correctly, the image did not deploy correctly.
Since I'm not very familiar with Azure, I only checked that the pipeline ran correctly, image was built and pushed. But I missed checking that the actual CD task deployed the image successfully, which it didn't.
As I'm sure many are aware, admob needed an update to use a newer SDK (7.64+) and this message appears on your admob account if you have apps using an SDK below that version:
Some of your iOS apps require a GMA SDK update To keep ads serving normally and minimize a loss in ad revenue, implement the GMA SDK 7.64.0 (or later) for your iOS apps. And configure the SKAdNetwork in your apps with Google's network ID.
Expo had a PR here that was merged 6 days ago. This should have updated the GMA SDK to 7.69.0. However, when I ran expo upgrade it states that it updated expo-ads-admob,
✅ The following packages were updated:
expo-ads-admob, expo-av, expo-keep-awake, expo-updates, react-native, react, react-dom, #babel/core, react-native-web, babel-preset-expo, expo
but no changes actually take effect. And if I have the newer version (10.0.0) that I manually installed as stated below, it downgrades it to 8.4.0.
When that wasn't working, I then went and manually updated expo-ads-admob to 10.0.0 via npm (also tried yarn) and it looked like the node package was actually updated (checking the CHANGELOG and it has info about 10.0.0).
Still when I build my app with expo build:ios, run the new app, and check my GMA SDK version on admob it is still using 7.55.1.
I have also tried completely removing expo-ads-admob and reinstalling, but the same issue occurs.
Any ideas as to why this is occurring? Is there some other method I should be using to upgrade to the latest commit on expo's master branch?
Appreciate all the assistance in advance and let me know if there is any additional info I can provide.
Additional Info:
SDK Version: 40.0.0
Platform: iOS
Workflow: Managed
EDIT: Received answer from Expo member, see answer below.
You cannot use updated packages if using the managed workflow, it must be bare workflow in order to update module versions manually. Therefore, this admob update won't take place for managed workflows until expo SDK 41 is released.
See expo forum here for more.
I am working with Speechly API in my react application. In that, I imported PushToTalkButton and PushToTalkButtonContainer from #speechly/react-ui and I have also configured from Speechly Playground it's working fine in Playground. Then I click on the button(PushToTalkButton) in react application it is not capturing my voice and not using the microphone. I tried to find out the problem with ErrorPanel but nothing is showing.
Could you try upgrading to version 1.2.4 by issuing npm install #speechly/react-ui#latest
Earlier versions were inadvertently coupled with a certain version of react-client package and might cause a problem you described.
I was working on a minor update to an app already accepted and available in the Apple App Store, and when I uploaded the new version, I got an e-mail that the binary was rejected because:
ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no
longer accepted. Instead, use WKWebView for improved security and
reliability. Learn more
(https://developer.apple.com/documentation/uikit/uiwebview).
How do I go about doing that? Is there a build hint or something?
Additional Information:
My app is using some CN1 extensions:
SENSORS,
BLUETOOTHLE,
JSON (required for BLUETOOTHLE)
As the BLUETOOTHLE extension uses a Cordova plugin, and Cordova was using UIWebView, I think that is the likely source.
According to Cordova's issue tracker, the Cordova plugin doesn't use UIWebView in its latest. It is possible that the build server has an old version cached. Try explicitly setting the version to 6.1 by adding the following build hint:
ios.pods=Cordova ~> 6.1
You'll already have this build hint, you just need to add the "~> 6.1" part.
Please post to indicate whether this fixed your issue, and I'll update the cn1lib to automatically add the version to the build hint.
Codename One doesn't use UIWebView at all. Make sure all your cn1libs are up to date and list them. Review your own native code and dependencies if you have any to make sure there's no usage there.