I don't get it!
I've been working with Ionic 3 for months now. I've had no trouble with builds. But for some reason now, every time I build I get the same version of code I previously had.
I've update cordova, so I have cordova 8.
I've deleted my ios platform and rebuild
I've done everything I can think of, and still I can't get the code to update through 'ionic cordova run ios' or through resetting versions and rebuilding through XCode.
I see others have run into this and none of their solutions have worked.
Has anyone figured out what's going on???
This is a big stretch, but I've run into this when using things like Code Push. I'll deploy my latest code to the device, forgetting that after startup Code Push will just go out and grab whatever code I deployed to Code Push last.
Another solution is to run following:
cordova clean
Did you update your Xcode to a beta version? This happened to me after I had updated to Xcode 10 Beta and I had to revert back to Xcode 9. Check your 'xcode-select' output and reset it to the defaults.
Related
When I run updated code of my application, it first builds the previous version of my app and then on rebuilding it, it runs the updated version of my app. Where the problem located? And as well, I'm a new bie at flutter...
Look of app on first run
Look of app after re-running
[]
How can I always get the updated code version of app on first run?
Run Flutter clean command in the terminal.
Actually we must remove/clean the cache of previous App so for that sake, We can run Flutter clean command in the terminal to avoid this problem.
my Ionic Devapp randomly stopped working properly. Not sure what I did to cause this.
When I serve my app and open it on the dev app, it opens per norm and everything works. If I close it and reboot it, I get the error
"Module card.io.cordova.mobilesdk.CardIO does not exist."
When I tap "Close", it just gives me a white screen.
Note: I do not use Card.IO in my project, however at some point in the far past I did install Card.io on this project but then removed it. It's been working fine ever since up until now.
I tried adding Card.IO back to the project with:
ionic cordova plugin add card.io.cordova.mobilesdk
npm install #ionic-native/card-io
To see if that would make it happy, but it's still throwing the same error message.
Just wondering if anyone else ever ran into this/has any insight on how to fix this?
I will start a project at the beginning of 2019 (January or February). Maybe a bit later.
Will it be better to start with the current version (3.9) , or should I start with version 4 which is currently on Beta but may be released soon. depending on the Ionic team life-cycle development. Any advise ideas are welcome
Any info about their roadmap?
I know it's not the best location to ask ... But I think that some people are wondering the same question!
revision
Thanks in advance
No, it is not. I recently upgraded my project from 3.19 to 4 and I regret doing so. I knew I might have this problem. I proceeded anyway as my cli would not desist from troubling to ugrade to the latest version.
First, I had problem with platforms, especially android platform. Later, I could not build. Then it started giving me all sorts of incomprehensible gradle errors.
I did all I could, I removed plaforms folder, added again, removed node_modules, run npm install again. Nope nothing worked.
Now I am going back to my earlier version.
So in my opinion, don't use it for production.
I am currently working with multiple Ionic 4 projects, I would have to say that the documentation is not the best for this version. There are still bugs here and there and some package issues (e.g. ionic-native packages) but seems to be in the right direction. It is a personal decision which one to use based on your project.
I personally prefer to go with Ionic 4 since the angular adaptation makes it easier for me to work around.
I have tried the beta version and also updated one of my projects from version 3 to version 4 and got a lot of errors. I think we have to wait for the actual release.
Problem
When I release a new version to the production channel in Ionic Pro Deploy (Channels) then I have to cycle my app twice in order to get the latest version. Even worse, on the first cycle my app reverts back to a far earlier version for some reason.
What I mean by cycling is, starting from a state where the application is shut down and not open, I open the app, wait for the splash screen to go away and app to be ready, and then close the app.
Question
How do I get my app to download the latest version on the very next time I open the Ionic app following my production release?
Plugin configuration
I used the plugin config from the dashboard.ionicjs.com page:
cordova plugin add cordova-plugin-ionic --save \
--variable APP_ID="[myappid]" \
--variable CHANNEL_NAME="Production" \
--variable UPDATE_METHOD="background"
Execute the command you already showed but set UPDATE_METHOD to "auto"
If you wand more control over your updating methods have a look at this:
https://ionicframework.com/docs/pro/deploy/plugin-api.html
In my case, live deploy worked correctly on a "blank" Ionic project. Live deploy also worked correctly on "my" app on iOS but not on Android.
I followed the follow steps and successfully fixed Android. However, during this process iOS suddenly had the same problem (would apply update on app install/close/open).
Set versions as per Ionic support. IonicPro live deploy currently requires these versions. Ionic are in the process of fixing this dependency:
"cordova-plugin-ionic-webview": "1.1.19",
"cordova-plugin-ionic": "4.1.7",
Install a new version of "blank" project. Update my app to use the same npm plugin versions (some of my app plugins were old).
Remove/add android platform. My hunch is this is what ultimately resolved the issue.
I wanted to try a remove/add ios platform to see if that also resolved the issue on iOS. But it was less work to ultimately switch over to IonicPro rather than re-config the local build setup.
Live deploy worked correctly on both iOS and Android after creating binaries in IonicPro.
So I tried implementing Facebook Login and followed all the steps accordingly. After having errors with FBSDKcorekit/FBSDKcorekit.h' file not found, I decided to pivot over to working on other components.
Lo' and behold, I have this error giving me trouble now. I followed along with this video: https://www.youtube.com/watch?v=rAXVKapP5cM&t=458s where I used the react-native install react-native-fbsdk and react-native link react-native-fbsdk commands in my terminal.
If it helps, I'm getting the following compile error in my terminal:
The following build commands failed:
CompileC /Users/someUser/desiredProject/ios/build/Build/Intermediates/RCTFBSDK.build/Debug-iphonesimulator/RCTFBSDK.build/Objects-normal/x86_64/RCTFBSDKGraphRequestManager.o RCTFBSDK/core/RCTFBSDKGraphRequestManager.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
I'm not sure if it was the tinkering around with the react-native-fbsdk or making links to it that caused this error. Note my project was working before I was trying to implement Facebook Login and using the link command.
What's going on here?
Thanks in advance for your time and patience.
edit: Also I did not implement any of the Facebook login code yet since I couldn't get a successful build on Xcode.
#kdizzle Make sure you have the right packager running in the terminal, sometimes you may have a packager associated with another react native project running, this happens because when you stop running an xcode RN project, it doesn't stop the packager in the terminal, and when you start/open another RN project in xcode, it simply checks if a packager is running, doesn't check if it's associated with the current project. So make sure you stop all of the packager instances in the terminal and then open the RN project again.
This may happen when upgrading a project to a newer version of react-native. To fix it,
Stop your packager.
Quit your iOS/android simulator.
Reinstall your modules: rm -rf node_modules && npm install
Restart your packager and simulator, e.g. react-native run-ios
I had this issue and it happened when I changed Hardware within the simulator. To fix it I had to kill the packager and run 'react-native run-ios' again. It didn't happen all the time but when it did this fixed it for me!
Another use is in a Brownfield App. Check your iOS and/or Android react-native versions. If they don't match exactly you will see this error screen too.
For example: I had a react native instance running 0.45.1 while Android had 0.45.0 installed. The solution for me was to make sure everything was running the same version.
None of the above answers have worked for me, so I researched the 'react-native' options a little and ended up:
Deleting the iOS and android folders from the app directory altogether
Running 'react-native eject'
Re-running 'react-native run-ios'
After that the iPhone emulator seemed to have no problem with the app.
This problem would appear when React Native libraries in ios project can not found.
I happend to meet this problem when i update my react-native version from 0.42 to 0.44, and cause that a file named RCTConvert+Map disappear in 0.44, so i update my pod.
command: pod update