I'm using Xcode 7.0.1 (7A1001) and noticed that Submitting my app now goes through an App Thinning stage and a folder gets created with the numerous .ipa for the different devices supported by our app.
When I'm downloading the app from iTunes Connect Test Flight for testing, I don't see any reduction in size. Can someone shed some light on whether the app size should be smaller? Am I doing something wrong in the configuration or will it only be smaller when downloaded from the actual App Store?
Thanks!
Related
I would like to view trace statements from my AIR iOS app that has been packaged for production using an AppStore provisioning profile and downloaded from TestFlight.
Does anyone know if this is possible?
You can't get the console.log or traces from a testflight app cause it is already distributed. You can only have access to those while testing / debugging. You can use a log system (like Firebase analytics for example) to check those traces.
Some more information about how to access logs in general, can be found here.
I am new to iOS platform(SWIFT - iOS9- Xcode7.3), I developed one Social Networking app in Swift and want to see crash reports of the app in the mobile as well as in Xcode. I did the process of Certifications,App ID, Provisioning Certificates and all...(whether all these are necessary for testing the app) I started with test-flight but I am not finding their SDK. So how to go with the step by step process of testing the iOS app before I go with the production.
Let me know if there are any other tools other than test flight. or What is the right way to do the process of testing and then production to the Apple Store. I dint find any proper answers please help.
Test flight is integrated with apple iTuneConnect app store build,As of now you can not get the crash report for beta build. App store build will not share the crash report to developer until it was not shared by user device (by enabling Share with app developer setting).There are many crash reporting tools
I will recommend to use fabric
I've created a Mac App for Mavericks that uses MapKit. It works fine during development and testing on Xcode 5.1. Now I'd like to submit it to the App Store and I need a Distribution Profile which I've created successfully. Trouble is, as soon as I add it to my project, the app doesn't run anymore - it crashes every time without fail with this error message:
When I change back to "no provisioning profile", or to the profile that Xcode created during development, the app runs again.
My question: Is this expected behaviour, or will the app be rejected by the review team? I know that iOS apps don't run with their distribution profiles, but I'm new to Mac Development. Any insights into this way too complex topic are appreciated!
My app was approved - and the crash was indeed no issue for the app review team.
I had a chat with Apple about this who were kind enough to call me back and explain the issue. Looks like this phenomenon is "kind of" expected behaviour: Mac Apps may or may not crash when run with a Distribution Profile.
To avoid this problem, we can add both a Development AND a Distribution Profile to our app, without one having to replace the other. This was news to me. Had I however opened my tired eyes a bit wider I would have perhaps spotted the little disclosure triangle myself:
Perhaps this helps those with the same issue.
In iOS6 I used to install some of my apps over an adhoc network without internet sharing. So the iPad had no internet connection. Therefore I use a typical html and plist file. Everything was alright.
Now, in iOS7 the installation is not working anymore. It is just stuck in "Waiting" and nothing more happens. (Note: It is still working on my iOS6 iPad)
First I thought something might be wrong with my plist, but then I copied the files to my IIS Server and installed it from there. Here I had a internet connection on my iPad and everything worked out.
Is it possible that the wireless distribution now needs an internet connection in iOS7 e.g. to check the ipa in the app store or something like that? Because this is the only difference I can see.
The app is signed with a valid distribution profile.
Thanks for your help.
It turned out the installation of apps over the air in iOS 7 really needs an internet connection now. The iPad tries to contact at least the following URLs before installing the app.
ax.init.itunes.apple.com: The device obtains the current file-size limit for downloading apps over the cellular network.
ocsp.apple.com: The device contacts this site to check the status of the distribution certificate used to sign the provisioning profile.
It seems in iOS6 it was ok if those URLs were not reachable and now in iOS 7 they have to be reachable.
Well i just had the same problem and I figured it out. At least on my xcode this is what happened. Turns out the application target release code siging identities auto set to developer and not their current state, from xcode 4.x, which is distribution. So when I went to distribute my application I kept getting the same error you had. So Click on your project name in your project explorer then click on the application target, not the project, and make sure the code signing identity is not set to developer for your releases. I have no idea why the code signing identities were automatically set to the developer profile, maybe there was some sort of bug when updating from xcdoe 4.x to xcode 5 that caused this. But now other devices are able to install the program. Hope this helps.
I have made iOS apps in the past but this is my first desktop mac app. We have a strange problem. I build for archive, validate it and send to test users. The app loads but doesn't get past the splash screen for those users. I tested with two non-developer users on my machine (same machine as development) and the same thing - it stalls on the splash screen in both Lion and Mtn Lion. For the two developer users, it is working fine.
Now something tells me there's a permissions or signing problem. But if that's the case, wouldn't the app not load at all? The other thing is that we are writing to the Library/Application Support folder. For these test users all the files that are supposed to be there are there - so the app is launching and writing.
Does this problem sound familiar at all or any tips on how to diagnose?