I had included the testflight sdk in my app but then decided to remove it. I have removed the library, and al references to it in my Xcode project. Now, when I run the app on my iPad from xcode, the app that gets installed on my iPad is testflight free. However, when I create an ipa and transfer it to my iPad, it contains the testflight sdk and the console log says testflight session started on every launch.
I have delete all kinds of caches and have done this a few dozen times over, but can't remove Testflight from my SDK. Anyone know which caches might be responsible for this?
Try to 'move to trash' the whole library files.
Related
I have just release an app to the App Store.
I have tested the build using TestFlight and everything worked.
After installing it from App Store it crashes upon opening.
Switching back to the same build but installed through TestFlight makes it work once again.
Does anyone know of any difference between a TestFlight version and an App Store version (of the same build), or have experienced anything similar?
The issue appears to be network related (I think, but I have very little information, and can’t setup a test env as it only happened after releasing to the App Store) and the issue is reproducible on multiple devices.
The app is a React Native (Expo build with EAS) and the source in its entirety can be found at https://github.com/pictoroma/app/
Edit: added source url
Resubmitted another build using the same source, and now everything works. Maybe something inside Apple’s pipeline corrupted the binary between TestFlight and App Store 🤷
My testers have problem with an app I had uploaded to Fabric Beta. During normal testing they uninstall already installed app from their devices and they download new version from Fabric. In that case everything works fine. App will download and launch properly.
Problems begins when they want to test situation when future app's users update my app from AppStore. My testers want to check if updated app will not crash.
Test case is easy:
List item
Download app from AppStore.
Launch it.
Download new version from Fabric (new version should override old)
Launch it.
App should not crash.
Problem appears in (4), Fabric shows error "download problem detected". (Note that everything works if there is no old app on device.).
Fabric has problems with overriding apps?
Fabric (1.7.7)
iOS 11
iPhone 6s Plus
PS. This test is important. Crash will appears when I change database model without migration for example.
Paul from Fabric here. Did you uninstall the App Store version of your app first? Since iOS 9, Apple changed its policy to prevent apps from being installed over the existing App Store version by 3rd parties, so you need to delete the original app before installing the Beta version. For more information, see our docs here: https://docs.fabric.io/apple/beta/tester-experience.html.
And the other reason could be if any other app is installing or updating parallelly, Fabric will not be able to install. Just faced the issue :)
I have trying to make an ios app out of libgdx. I have an Ipad (no iphone yet) an I am trying to upload my app to the device. I have an XCode 7.2, which means that it guarantees that I can upload an app to an apple device without an Apple Developer Account, which currently I have none. I had successfully uploaded an app onto my Ipad with XCode alone. In Eclipse, a simple test app runs perfectly on an IOS Simulator. But when I tried to run it in an IOS device, it does not work. Since it is just a free provision, I was hoping this would work. The Bundle identifier of the xcode app with free provisioning is the same as the app id and main class of my eclipse ios app. Before this, there was an error that no provision was set, so I set the bundle identifier of the xcode app the same with the eclipse app, according to roboVM(http://docs.robovm.com/getting-started/provisioning.html#free-provisioning). But then this error shows up,
"Launch IOS Device App" has encountered a problem.
Launch failed. Check the RoboVM console for more information.
The given data is not a property list of a supported format.
I need to test my app on a real device because I am going to try to implement an online multiplayer with it. As of now I am still using LibGDX 1.5.5. Is it because roboVM needs an apple developer account?
Edit: Even without any device connected, the error persists
I had the same problem as the original poster and it persists in IntelliJ. After some tinkering, it was also showing up on the command line. THanks to some help on the libgdx irc forum, we coudl solve the problem. It was due to running iOS 9.2 on my iOS device and a too old robovm-plugin 1.12.0 seems not to work with libgdx and iOS 9.2. An upgrade to 1.12.1.-SNAPSHOT solved it.
Attention, you have to update two lines in build.gradle:
in buildscript - dependencies: classpath 'org.robovm:robovm-gradle-plugin:1.12.1-SNAPSHOT'
in allprojects - ext: roboVMVersion = '1.12.1-SNAPSHOT'
If you want to compile in IntelliJ, you need to manually install the nightly robovm-plugin from the nightlies download section from the robovm webpage.
I downloaded Xcode 7.1 from the App Store today after working from 7.1 beta downloads from developer.apple.com and have a new iOS app build to upload. So I did:
Product > Archive
Upload to App Store (or Validate)
But the response was:
You are not authorised to use this service
Intriguingly, when I 'Export' the build to the Desktop and then use Application Loader 3, it uploads without error.
Is this an iTunes Connect bug? Or is there a new Xcode checkbox I've missed?
Note: I've also tried removing and re-adding my AppleID as suggested here, and restarted my Mac for good measure (which actually allowed the validation to work once), but still no luck uploading directly from Xcode > Organiser.
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool -->
Application Loader
Double click "Deliver Your App" and choose the
file exported in step #2
click next and follow the instructions until
the end
Here's the quick solution:
Don't use Xcode beta versions to submit apps for release — it's beta for a reason and shouldn't be used with production code.
Submitting Apps
Apps that are created using beta versions of Xcode or that are built
for beta versions of operating systems will not be accepted on the App
Store and Mac App Store. Apps that you submit should be developed
using the latest version of Xcode from the Mac App Store and should be
built for publicly available versions of iOS, OS X, and watchOS —
except when GM seeds are available. When a GM Seed of Xcode becomes
available, use it to develop your app for submission. When GM seeds of
iOS, OS X, or watchOS become available, build your app for these
versions.
↳ https://developer.apple.com/support/pre-release-software/
Having the same problems as all of you, just thought I'd share that I found a way to Validate successfully, you have to disable the "Include bitcode" checkbox before moving forward. As for the actual upload to App Store, no work around for that one other than use the Application Loader...
Also I've been seeing this too since XCode 6.4, but it seems once the current version has a couple of months after it's originally released it starts working again... fingers crossed that it starts working again soon, because uploading straight from Organizer is so much better. (I saw the Beta Version post, when I say after a couple of months for current version I'm not talking about Beta versions, just in case ;) )
Same problem here.
Downloaded Xcode 7.1 from the App Store and it refuses to upload a new version.
Happily Application Loader worked ;)
Hopefully this gets fixed quickly.
One possible reason for the issue could be multiple development accounts under one name (personal and company). I've read elsewhere (apple radar) that that caused earlier problems of this kind.
Happens here if the dev account is only admin. I had to use the central account for uploading our apps. I think this problem startet sometime with XCode 6. Didnt investigate further though since Application Loader works in cases when I dont have access to the central account.
I also have the same problem today.
Finally, I used the application loader to upload successfully,too.
Theres a few solutions I have come across to solve this issue.
Most common being to remove and re-add your developer account.
This won't work on its own though, you need to also 'view details' on your account and have Xcode download your provisioning profiles again.
The other alternative is to upload your build using application loader. The disadvantage to using this solution is that should you be trying to upload using a beta build of Xcode or OSX you won't be able to change your apps .plist in the archive folder to trick iTunes connect into accepting it. In this instance all you have access to is your ipa.
Disable the "Include bitcode" checkbox worked for me.
I want to distribute my app to testers using dropbox.The links I followed were
http://dr-palaniraja.blogspot.in/2011/06/distribute-your-iphoneipad-adhoc-builds.html
Error when distributing an IPA over the air with dropbox - iOS 7.1
Finally I created Html and when I click on that it shows an alert “dropbox.com would to to install app”. But when I click on that nothing happening instead of installing…
What might be the chances of failure(My device IPAD2, OS-8.1.3 )
Console log Info:http://pastebin.com/3WbgjT6Q
Thank you.
You can use app loader to distribute beta version to your testers. It is very simple and fast. I am using it after closed testflight .