I just upgraded to xCode 4.3 and used it to generate a new revision of an iPad app about 50 beta testers have been using for several months. I distributed the beta app through TestFlight as usual.
Most testers upgraded with no problem, but several testers are getting the TestFlight message "You have not permitted this device to install this build" when they try to install the new rev. I've never seen this message before. Their iPad UDID is definitely in the build's embedded.mobileprovision file and everything was working working fine with the prior revision.
What am I -- or the testers -- doing wrong and how do we correct it?
Hi i experienced the same and it seems that you must generate your mobile provisioner profile from Xcode(instead of Apple dev site for example) and you should update your App permissions (TestFlight) with this same provisioner profile that you just generated on your machine so basically the machine that generates and archive the apps using Xcode must generate the provisioner profile and then you should update your testflight app permissions with this file.
Does that make any sense?
Hope this works for you testflight is really nice to use, i faced same problems with all of my apps and hardware devices (testers all around the world)
Thanks
Turns out this is apparently a bug in Testflight. I tried to resolve the issue through their support forum and multiple emails with no real answer. I did not want to switch services as my testers knew the Testflight system well. But eventually switched to Diawi. My testers were able to install the app using Diawi with no problems.
Related
I have a testing and production release channel, on TestFlight and the App Store, respectively. I want the ability to run both on the same device. Otherwise if there is an issue with my testing release channel me and my beta users are blocked from using the working production channel (as least without constantly downloading and overwriting the TestFlight vs App Store versions)
I tried https://medium.com/#ywongcode/building-multiple-versions-of-a-react-native-app-4361252ddde5, but it seems like most of the configurations were reverted on build, and I wound up with the same bundleIdentifier and therefore I could not download the TestFlight testing version without removing the App Store version.
I think your best bet is to release multiple apps from 1 source code. We ran into this problem as well and ended up releasing separate test (internal testing), beta (external testing) and production apps. Each with their own app logo, app name and expo release channel. As far as I know, there is no way to switch release channel after your app has been built.
Alternatively you could (beta) test your app by pointing your users to https://exp.host/#username/yourApp?release-channel=. This way your testers can test most of your app’s functionally in the Expo Go app.
You can use iOS Build Configurations and Android Build Variants to easily create different apps within one project.
I'm trying to install my iOS app on to devices running iOS 7.0. I can install them on my iPhone 4 with iOS 5.1 jailbroken. But currently I'm not able to do so on a friend iPad 4 with iOS 7.0.
For installing them on JB devices I'm using JailCoder .
It works without any problem and I can code and compile my test apps, and put them on JB devices without any effort.
Recently trying to investigate possibilities I found an application named PP25 for Windows, it is a chinese application and it is said to be able to install cracked apps on NON-JB devices.
So i tried to see ig it works somehow, I was able to get my apps converted as ipas from my phone and download them to desktop with it, and i can then upload on other JB devices, thanks to a Cydia application named AppSync, pretty good indeed, but I tried and wasn't able to install them on iOS 7.
That was disappointing, I made additional tests and it appears that the PP Assistant application is able to install cracked apps on iOS 7.0 too, but not my unsigned apps (fails to verify the app rights).
Indeed there is a section in the chinese application where you can download and install commercial apps on iOS 7.0, so there must be a trick they use to re-sign the apps to make it appear as it's a legit app and thus be able to upload to the device even if not jailbroken.
If someone has any idea of what they actually do to make this happen, this would be very useful to know to test apps without JB on every device.
Non-jailbroken devices require valid code-signing to execute binaries. Either wait for a jailbreak to surface for iOS7.X, or find a code-signing service (they are available out there).
Using Xcode 7, you can install your app to your device using a freely available Apple ID.
Free On-Device Development
Now everyone can run and test their own app on a device—for free. You can run and debug your own creations on a Mac, iPhone, iPad, iPod touch, or Apple Watch without any fees, and no programs to join. All you need to do is enter your free Apple ID into Xcode. You can even use the same Apple ID you already use for the App Store or iTunes. Once you’ve perfected your app the Apple Developer Program can help you get it on the App Store.
See Launching Your App on Devices for detailed information about installing and running on devices.
Source
I've installed Testflight (1.2 B3) as stated in the documentation. Builds are uploading and updating fine. I can see sessions (mostly anonymous :/), I receive the logs (TFLog) - but I do not receive any crash reports. I even introduced a crash-on-event (a method not found thing) - but theres is nothing on Testflight about it.
Provisioning is via a developer profile which embeds several devices.
The problem occurs on iOS6 and iOS5 / iPhone5 and iPad3. The is being build against iOS6.
Any ideas?
UPDATE
I've tested several other frameworks and ways to receive crash reports. Nothing worked so I suspect something in my code (obviously). Are there any other switches that XCode 4.5.1 might have enabled and that way disable any error reporting during a "production environment" like setup?
UPDATE 2
As of now we're using Testflight only for distribution of beta versions and switched to Crashlytics for crash reporting. It's a bit more streamlined and fetches most crashes.
I also do not get any crash reports via TestFlight. This is what the TestFlight people told me:
Our team is currently looking into an issue associated with auto
versioning of the app when uploaded and SDK data not reporting
properly. Looking at the URL you provided it looks like the build
version is not changing before uploading the app to TestFlight and our
auto versioning implementation is causing an issue with general SDK
data reporting.
I will share this with our team and we will contact you when we have
an update available.
I tried to update the build version to avoid auto-versioning, but it did not help me. But maybe this issue is hitting someone else.
Testflight did not satisfy our needs to log crashes. That is why we skipped to Crashlytics (as I said in the original post). The issues with Testflight seem not to be resolved. We still do use it for distribution, that is what it's good at.
I have a jailbroken iPhone 4 and i'm installing a iphone application from xcode to test it, this works fine. I also have a iPhone 3gs that was given by my university to install the application, this is also jailbroken but when i try to install it i get "a valid provisioning profile for this executable was not found". How can i fix this? (also i do have a developers account, my university lecturer added me but he hasnt activated the account yet and he takes ages to respond to emails -i need to test it now but not sure why that error appears?). Would appreciate some help on this matter..
I assume the provisioning profile you are running doesn't include the UDID of the device you're trying to run on. This requires logging in to the Provisioning Portal and adding the device, then downloading the new profile and installing it on your device.
I have a problem with an app that works perfect on my iPhone 4, and on my 3Gs but both are on iOS 4. BUT, when a colleague installed it on his 3G with 3.1.2 on it... it crashes on startup.
Is there someway I can test to install the app in a 3.1.2 simulator of some kind?
He didn't send me his crash logs yet.
Best regards,
Paul Peelen
I haven't done this for the simulator, but you can find links for the old SDKs here:
http://chris-fletcher.com/2010/08/28/howto-install-iphone-sdk-2-0-3-1-for-xcode-3-2/
You should be able to install the old simulator SDKs and have them show up in the simulator menu.
Dealing with multiple SDKs has proved to be extremely painful in my experience. If you end up installing an old SDK, I'd recommend you install it in a separate "Developer" folder.
In my opinion, the best way to deal with 3.x debugging is to get your hand on an old iPod touch with 3.x installed. You can get one for pretty cheap from a local classified ads site and it really makes 3.x debugging a lot easier.