New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚨 XCode 12 Status
#8867
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@bmacdonald We have published @nativescript/localize 5.0.1 now which contains the hooks fix mentioned regarding CFBundleDisplayName and CFBundleName. That is the {N} 7 compat version. Let us know if you need a backported fix to the hooks in nativescript-localize 4.x if planning on staying on 6.5.x for awhile (we will need to coordinate a patch with @EddyVerbruggen if needed there). |
This comment has been minimized.
This comment has been minimized.
|
@bmacdonald here's the fix for the 4.x series: EddyVerbruggen/nativescript-localize#100 |
|
Hello, I'm having a weird issue now on iOS. I have xCode 12, and i just updated nativescript using npm i -g nativescript@rc But my code is still for 6.x.x. Its working perfectly on simulator and I can run my app on 12.4 and 14.0 iOS. but when I send my app to Appcenter and download it on a real device running iOS 14, I'm gettin this weird error and can't even open the app. "App Name" Needs to be updated Has anyone else seen this issue? I'm completely stumped on it. |
|
@JCFowler I tried the NS 7 cli rc on my NS 6.5-project and it builds, but it can't deploy to App Store / Testflight, stating (that is with and without the ARCH-changes in Reverting back to using 6.8.0 of the CLI, the build succeeds and deploys correctly to Testflight. |
|
@timdoege
Are you able to build on simulators? But luckily on real devices, I am able to build and run! So Thank you so much!! |
This comment has been minimized.
This comment has been minimized.
Can you re-run the build command with @edgardksb same here - re-run with @timdoege Hmm, that's an odd one - could be related to the rc change, I'll have to test a release build. We may need to opt-out of this clause in release mode. In dev mode, this worked fine with an arm64 device (iPhone 6s) and x86_64 simulators (both ios14 and 13). (the current simulators are all x86_64). |
|
The symlink for the .app file is wrong in tl;dr, instead of |
|
@NathanWalker updated my project to 7.0.10 & tns-ios to 6.5.3..still i'm getting that linkage error -1 & Command xcodebuild failed with exit code 65.. :( : ( |
|
@RibuRoyson we would suggest emailing support@nativescript.org with system details like node, npm and a sample of your package.json - the quickest help would be to send details on how to access project and we’d be happy to help. |
@NathanWalker It looks like this is not yet fixed (Cli version 7.0.10, |
|
Updated my node to 12.18.4 performed npm i g natievscript & ns clean..still the xcode error occurs.. |
|
@ngrie Right, that's something we haven't fixed yet - but you should be able to change the @RibuRoyson share the project if able, we can't fix something we can't reproduce ourselves! |
@NathanWalker I was having this error and this solution has worked correctly for me. |
|
I just followed the steps to upgrade and managed to make my app work again on simulators/devices... and it uploaded correctly but during review i got an email saying any ideas what this means? and how to fix this? |
|
@eltharynd what runtime is that? |
|
@rigor789 Is my understanding correct that the problem is that the libraries I found a tmp workaround in #8937 |
|
Hello All, And from xcode Runtime initialization took 120ms my package.json Does anyone have any idea? I have this problem since last week and don't know what went wrong :( |
|
@SaifulZiko first of all try running And maybe share your |
|
@eltharynd thanks for your response ... after "tns clean" whenever I try to run "ns run ios" I get this warning regarding cocopods No issues were detected. |
|
@eltharynd After updating all ...NOW i AM GETTING THIS :( I have no idea from where this NS-cloud came ! |
|
@NathanWalker I was facing this issue - NativeScript/nativescript-cli/issues/4846 with latest CLI. Even though I run with |
|
Any news on the problems? Currently we are blocked in the daily work (nativescript/cli 7.0.10) tns-ios: 6.5.3? The only way to work is manually remove the excluded_architecture opening the project with xCode |
|
@limux82 I'm not sure about the 6.x version but this issue has been fixed on the 7.x latest release #8937 You might wanna migrate to that if possible |
|
Thanks I'm working on migrate to ns7, but it's not so simple when you have a big application with a lot of plugin with problem to migrate. I think that a framework has to be retro compatible in the build process, to avoid migration to other frameworks |
NS 7 requires XCode 12; Xcode 11 works with NS 6's cli... |
|
HI It's what we have done XCode 11, tns-core-modules 6.5.3 and CLI 6.8.0 warning: Mapping architecture armv7 to i386. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target '' from project '')warning: Mapping architecture armv7s to i386. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target '' from project '')warning: Mapping architecture arm64 to x86_64. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target '' from project '')warning: There are no architectures to compile for because all architectures in VALID_ARCHS (i386, x86_64) are also in EXCLUDED_ARCHS (i386, armv6, armv8, x86_64, arm64e). (in target '' from project '') The only way to resolve the problem with the simulator was to add In App_resources ios
I have also a branch with the configuration with Xcode 11, @nativescript/core 7.0.x and @nativescript/ios7.0.2-rc and the last CLI 7.0.10 and I have the same problem. In android, skipping 2-3 plugins that are not updated to 7 it runs, instead in ios same problem. Now I will install xCode 12 to see if works with NS7. But After that can I continue to work with NS6 (we are not ready to migrate to 7 with master branch)? In my opinion this issue should be reopen? |
|
We're still experiencing NativeScript/nativescript-cli#5411 with the latest |
It seems like the Previous builds with |
|
I still have this issue with the version of 7.0.12. Is anyone still facing this ?? My build is failing. |
|
I can't upgrade to ns7 due to plugin issues. |
rigor789 commentedSep 19, 2020
•
edited
Update (09/27):
We have released
nativescript@7.0.9-rc.2with additional fixes for running on a real device.Details in this PR: NativeScript/ios-device-lib#70
Update (09/23):
We have released
nativescript@7.0.9-rc.1with fixes for running on a real device. This version reverted some changes fromrc.0- we expect this to run fine for both simulators and devices, however there may be other cases we need to take into account. Please try the latest RC (ideally revert manual changes in Podfiles, build configs etc and runns clean) and if something isn't working, re-run with--log traceenable and share the logs with us.We released
nativescript@7.0.9-rc.0that should allow building nativescript apps for the simulator using XCode12.Please try it
And then cleaning your project (👍 on this issue to let us know - and if it fails to build/run leave a comment with the output logs (re-run the build with
ns clean) and re-running it. The apps should build successfully, and deploy to the simulator(s). If this works for you, consider leaving a--log traceto get more verbose logs).Known issues:
warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0- this is a warning, that should not cause any issues with the build. If the build fails, it's likely related to another issue.--release(and--env.production) not able to build the app. [Should Be OK in RC1]CFBundleNamethe cli will fail withNo .ipa found in /.../platforms/ios/build/Debug-iphoneos directory..[Looking into a fix]Related issues:
The text was updated successfully, but these errors were encountered: