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.
Related
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 using Google Cloud to deploy my application. I have followed the steps in the documentation for deploying. I deployed early on in my project and it was successful. I then decided to change some files and update some features in my app. For this i followed the documentation for updating a deployment. This update was successful. It had me create the deployment in my Deployment Manager and run the gcloud commands to commence update. When I redeployed with gcloud app deploy, it was successful.
I have since added a couple more lines of code and features in my application. I followed the same documentation for updating a deployment as I had the first time I made an update and it is no longer working for me.
Does anybody have any idea what would be the problem? Again, I was able to successfully deploy, and even update that deployment once by following Google Cloud docs. Now I am having no luck.
Have you been changing the version number? Go to:
https://console.cloud.google.com/appengine/versions?project=< your project name >&serviceId=default
And make sure the version you want is active. Also, you can try:
http://<VERSION>-dot-<SERVICE>-dot-<PROJECT_ID>.<REGION_ID>.r.appspot.com
Example:
https://20200813-dot-myapp.uc.r.appspot.com
if the version number was 20200813 and your appname is myapp and the region is uc
i will just start my question a little bit structured:
background information
I am developing a React App with Electron on my Mac.
The customer uses this app on Windows 7 and 10.
The app is packaged with asar on a gitlab runner within a docker
the dockerfile for the runner is from electronuserland/builder:base
What works?
If I start the App locally I run the npm build script and start electron -> The app works fine!
If I package the App locally (on my Mac) for Windows and copy the .exe to my VM: -> The app works fine!
What does not work?
If my pipeline get triggered by my commit the gitlab runner starts to run the buildscript and the package script (The same ones I run locally for packaging and running my app) The build is "successfully" completed and the artifacts are stored on gitlab.
Then I download the .exe from the gitlab artifacts on my Windows VM and install the software. This absolutely works fine. The app can start up and some functions are pretty good working.
But there is a problem with a package (or maybe some more, i do not know yet) It is the react-bootstrap-daterangepicker. It gives me an JS error with $this.$picker.daterangepicker is not a function
I googled a lot and found existing problems with the package, but I do not understand why it is working when i package the app locally and not with the runner.
I removed my node-modules completey on my local machine and reinstalled them, and it is still working fine.
Do you have any idea?
Where could be a difference between my local environment and the runner environment that can cause this kind of problem?
I am pretty stuck in this problem, and you would be my hero if you can help me to fix this!
Have a nice day!
electron-builder recommends using electronuserland/builder:wine to build Windows targets. I'm not sure if this would fix the problem, but could you try using this image instead?
electronuserland/builder:wine — Wine, NodeJS 10 and required system dependencies. Based on builder:10. Use this image if you need to build Windows targets.
For more information: https://www.electron.build/multi-platform-build#provided-docker-images
I'm a bit confused by react-native-git-upgrade process flow, It seems to work fine, but it only updates packages in package.json, never native files in android or ios. These files are changed in my project i.e. changed app bundle id's, icons, launch screens etc... I am wondering if this is why it never updates them?
Also, what in release notes can indicate that something changed in native files, so we can use it as confirmation maybe?
if you check the documentation it says is automatic.
IMPORTANT: You don't have to install the new version of the
react-native package, it will be installed automatically.
Blockquote
But in case of any doubt you can always delete the ios and android folder, and do the following:
react-native eject
This command is gonna create the ios and android projects.
You should follow the documentation:
But if the above doesn't work to update, then is a different problem and I suggest to create an issue.
I made some fixes for my App and wanted to try it out today on my iPhone and now I can't install it on the device anymore. I'm getting the error "Unable to Download App" on the phone.
I haven't changed anything on my Apple Developer Account and yesterday everything was working fine. Is this a known bug and does anybody know how to fix this? My iPhone is of course registered and I also did the "iOS Certificate Wizard" and built it again but it didn't work either.
Edit: So I was able to install the app after doing the complete Certificate Wizard again with also overwriting everything (which I had not done before), but now I made another build and I can't install it again! Do I really have to do the Wizard thing every time I send a build now?
Are you trying to install a distribution build on top of a development build, or vice-versa? If so, uninstall the existing app first.