I'm developing iOS apps and I'd like to share my apps with TestFlight testers. This is not the problem and works fine (via email). However, when I'm uploading a new build, I'd like to have in-app updates.
The SDK describes this as being possible, but I don't see anything from an update in my app.
I closed the app from "Multitasking".
I added the SDK to my project and in the AppDelegate my TeamToken, Checkpoints, etc. work fine.
Any ideas?
On testflight, have you enabled the force upgrade? (Your Application -> Build -> Build information -> Forced upgrades)
Also please make sure that the activity report is showing your session when you start your app.
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.
The title of this question basically says it all. I enabled Crashlytics in my Today extension, and for some reasons, the dSYMs are not being uploaded, even though I'm not using Bitcode.
I tried uploading them manually (from ~/Library/Developer/Xcode/Derived Data/Timelines-evxmjnxmpmcivkavmpijzakaxkrp/Build/Products/Debug-iphoneos/Timelines.app.dSYM), but the web interface doesn't really give me any feedback. It shows this screen:
No matter how long I wait, once I refresh the page, it goes back to the 'upload dSYMS' screen.
I think the problem might be that the UUIDs of the missing dSYMs don't really match those that I found locally.
Some notes on my setup:
Xcode 8.2
Today extension running on iOS 10.2
Bitcode is not enabled.
Fabric and Crashlytics integration was done using CocoaPods.
Archive wasn't uploaded to App Store. I'm just testing it locally on my devices. But since the entry for crash reports was created in the web interface, I assume the automatic upload should work anyway.
My question basically is: how exactly can I upload the dSYMs manually? And, second one: how can I make the automatic upload of dSYMs work? Thank you.
It is described here completely ==> fabric.io.
As it said you can download it from activity tab in itunesconnect and then upload it to crashlytics website.
So i want to test an unreleased version of the app for deferred deep links. How do i do it? As the changes made will not be there in the app i download from the play store after redirecting.
Alex from Branch.io here: this is pretty easy to do! On your Branch dashboard under Settings -> Link Settings -> Android, select Custom URL, and put in the information requested.
Alternatively, you can delete the app from your phone, open the link, install a side-loaded build of the app (directly from Android Studio), and then manually launch the app. You'll still be deep linked to the correct place.
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've created a Ad Hoc distribution profile with a couple of devices. If I want to add a couple of devices to the profile, I have to create a new profile and a build in XCODE for my app with the assigned profile.
Is there a way to make this easier? A way to make the management of the devices more simple? Without rebuilding and redistributing the app.
I hope someone can help.
You can't change the list of devices an ad-hoc app will work on without at least re-signing with xcode and redistributing the app. Sorry! I suppose Apple feel it opens up non-appstore distribution methods if you can add devices to an app already out there.
In fact you can!!
You don't have to recompile your project again. You don't even have to open XCode.
All you have to do is create a new mobileprovision file and distribute it with the existing app.
Your end users have to download and install the new mobileprovision file and app, by this order.
Here is a step-by-step.
Hugo Maurício