After upgrade my app to Ionic 4, I always get this warning when uploading the app to app-store:
The app references non-public selectors in Payload|\app-name.app/app-name: transform
I've upgraded every component, downgraded new ones, and warning is always there....
Is there a way to know what plugin / component is causing it ???
Thanks you very much, and sorry for my english
Related
We are facing an issue with our new game download size on the store, we are using :
- Unity 5.0.2
- Xcode 7.0.1 (bitcode disabled)
After building the game with Unity and archiving it in xCode, if we export the archive to ipa ( Save for iOS App Store Deployment , without app symbols), the ipa size is 39.4MB, but when we submit the game to App Store (through xCode organizer directly, or using the Application Loader with the ipa), Testflight shows the game size to be 172.9 MB !!!! which is a huge problem, many players will not download the game because of that.
Any help will be much appreciated.
-Khaled
Testflight usually shows the size including symbols. Therefore it's important to mention that Testflight size != Appstore size. You can of course submit the symbols with your final Appstore submission as well, but this is not encountered for the download size limit. Apple adds some additional files to your submitted ipa but most importantly, it takes the binary and applies security measurements on the text segment which won't be compressed anymore afterwards and could increase the final size.
Anyway, you need to upgrade to a newer Unity Version, as 5.0.2 includes a quite outdated IL2CPP version which improved a lot in the last year. There is a guide on how to receive proper values and also some tips in the Unity forums about it.
http://forum.unity3d.com/threads/il2cpp-build-size-improvements.322079/
I solved this problem! Just move back to xcode 6.4 version! :)
I have been trying to submit my app multiple times to the app store and I keep seeing this error:
Invalid Swift Support - The files libswiftPassKit.dylib,
libswiftCoreAudio.dylib, libswiftContacts.dylib,
libswiftCoreLocation.dylib, libswiftCoreMedia.dylib,
libswiftCoreData.dylib, libswiftAVFoundation.dylib don’t match
/Payload/MyApp.app/Frameworks/libswiftPassKit.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreAudio.dylib,
/Payload/MyApp.app/Frameworks/libswiftContacts.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreLocation.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreMedia.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreData.dylib,
/Payload/MyApp.app/Frameworks/libswiftAVFoundation.dylib. Make sure
the files are correct, rebuild your app, and resubmit it. Don’t apply
post-processing to
/Payload/MyApp.app/Frameworks/libswiftPassKit.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreAudio.dylib,
/Payload/MyApp.app/Frameworks/libswiftContacts.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreLocation.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreMedia.dylib,
/Payload/MyApp.app/Frameworks/libswiftCoreData.dylib,
/Payload/MyApp.app/Frameworks/libswiftAVFoundation.dylib.
Is there something else i'm doing wrong? Or is it still not available? I'm not able to find any resources to help with the above
Seems like it's an issue with Cocoapods. As per below:
https://github.com/CocoaPods/CocoaPods/issues/4188
The current latest version of Cocoapods is 0.39 beta 4 which does NOT work.
You can check your
Build Settings -> Embedded Content Contains Swift Code.
If it's NO,you can set it to YES,and then have a try.If it's not working.You can update your Mac system to Mac OS X 10.10.5 and your Xcode to Xcode 7,just rebuild your project with iOS 9,and then Xcode will tell you which you must deal with.
I have an app published in the store, which i want to change so much its internal working, that i decided to start over. I successfully finished the new version of my app, but when i install the previous version of the app, and run the new version from xcode to check if everything is compatible, i get "Could not change executable permissions on the application".
What i did was to change the bundle identifier of the new version of the app to match the old one, but i cant get it to run under the same name. Do I need to do something else? The app runs great if the old one isn't installed, but when I have the old one installed, and I want to run the new one, so it replaces the old one, i get the error i mentioned above.
Thanks
The problem I had was related with the use of unreleased iOS beta software. It is solved by testing my apps on a device running the last released OS (iOS 5.1.1 at the moment).
i think you should try to remove the app that have same bundle identifier in you iOS device ,
hope this can help you!
I just had this same issue which almost caused me a meltdown. I'm on xcode 5.1 and ios 6. My answer was to delete the app on my iPad by holding my figure over the app icon, then pressing the 'x' that appears next to it. Then I went back into xcode and built the project.
i use xcode 4.3.2 with phonegap 1.6. my app runs well the first time, but if i close the app in the ios simulator and i launch it for the second time, it crashes. Why?
This is probably only in the simulator. I have had it a couple of times in the simulator but it never happened to me on-device.
I am currently having this issue, except in Android. This is with the release flag. More info can be found here: https://forum.ionicframework.com/t/v2-android-second-app-start-doesnt-work-for-release-version/125583
but here is a copy pasta in case the link goes down:
Synopsis:
My app has a canvas on it on the page html. On second start of initial install, app start doesn’t show canvas. I know because the body tag has a background and the canvas has a different background. The page does not have a module defined for it. This is only when built with --release
Environment:
Ionic: 3.20
Cordova: 7.1.0
Angular: 5.2.9
Android: 6.1.2 (I think build target 25)
jdk: 1.8
Additional Info:
I am sort of doing bleeding edge stuff, but I am now out of the realm of being able to solve this on my own. I am using pixi.js, specifically from an additional interface library called angular2pixi. A2p doesn’t support --aot building.
Before I go on, let me reiterate everything works, even on multiple app restarts for everything other than --release.
The top level architecture is fairly simple:
a2p provides a service that has an instance of pixi. My app uses that service and has a page with a canvas awaiting Pixi’s rendering. When the app initializes, it starts up the pixi service, passing it the canvas reference and voila: html5ified angular.
I have offloaded the actual initialization of the rendering to a user clicked button to make sure it’s not something to do with life cycles but that didn’t work either. Even more interestingly, the button I made didn’t show when the app didn’t load. So likely, this means the ion-content itself isn’t showing!
Most interestingly, if I go into app info and delete storage (not cache) then it works on next app start! I am using localstorage but I attempted removing all mentions of it and no luck. ALSO On second install, or rather what would more technically be an update, the app works on every start after that.
This happens on android and I can’t seem to replicate it in iOS other than the first time I tried. Because it is a release build, it’s difficult to debug. I attempted using Ionic Pro Monitoring to no avail.
So far, my leanings are:
some type of caching causing a bug with the canvas itself
an error that is causing cordova or ionic to terminate
problem with my build process
a2p’s architecture (how could I go about debugging this given I have little knowledge of the underlying mechanics of cordova/ng2 -> native compilation?)
a cordova plugin (perhaps causing one of the above)
So as you can probably tell from my formatting, I’m somewhere between nerd heaven and hell. Such a fascinating problem… but plis halp
Hi I have the following problem.
I am almost finished with creating a new update for my app.
Now I wanted to try if when I install an old version of my app and then run the new version of this app via Xcode on my iPhone.
If the app gets updated correctly to the new version.
Unfortunately this is not the case. I ran into a few problems:
the icon does not get updated (only looses the shine cause the new
one does not have on)
at the start screen of the app there are still parts of the old
version visible like buttons and labels
most of the app gets updated to the new version correctly.
is this a bug or problem from Xcode or will this be the same when my customers update via Appstore?
This problem won't be there when your customer updates via Apple. I have seen problems like this only during debug.