I am making an app that collects information from Apple Health (HealthKit). When the application is installed for the first time, the apple screen appears with the permissions that will be used, but when it is in Testflight that screen never appears, is there any extra configuration that has to be done when it is released to production?
if the app is installed from xcode, it works correctly
I had two different bundles, one both in the card of my app and another service that I have OneSignalNotificationServiceExtension. Within both they must point to release and not to debug. that's what i did and it worked in testFlight
Related
I have an app that contains a Today Widget and it's working fine during debug as well as the first version distributed using TestFlight & HockeyApp.
The problem occurs when the user updates to a newer build through their service. The widget seems to just show the snapshot and never actually initializes (I print out logs when it gets to certain parts of my view controller but I'm not seeing those).
To fix this problem the user will have to restart their device or delete and install the app again.
Does anyone know of this issue and/or how to fix this?
I've seen the same issue using OTA installation (Testflight web, HockeyApp) but it seems to work fine distributing through the new Apple Testflight app.
I would suggest filing a radar ticket to Apple if you plan to continue distributing apps with widgets through OTA methods. Personally I've just switched over to using the new Apple Testflight app to distribute my betas.
I'm trying to install my prov. profile via email,itunes. When I try to tap the prov. profile in email it just directs me to settings. I believe that there should be a pop up that ask to install the prov. profile but I see none. Did I forget any important parts that cause this trouble or maybe its a bug from new iOS 8 update?
"It's not a bug, it's a feature". Apple has purposely made it so that they can no longer be installed manually by a user and must be installed by dev tools such as Xcode or device management systems such as MDM. Additionally, they are no longer shown in Profiles & Device Management and are not removable by the everyday user either.
With iOS 8, Apple has moved to the model that any flow that requires the everyday user to install, remove, or even think about provisioning profiles is flawed and that iOS should handle this automatically on the user's behalf. If the provisioning profile is expired, iOS should get rid of it automatically. As apps are deleted, iOS should properly deal with the provisioning aspects automatically. This philosophy is mentioned in WWDC 2014's talk on Managing Apple Devices around ~42 minutes in.
I guess it's a bug. I'm having the same issue with Testflight.
As a workaround install the profile using Xcode's 'Devices' view.
I'm a newbie in OSX Development. I built an application in which will be distributed outside the Mac App Store. I have all the other certificates and keys working except for the Developer ID (App and Installer) for production.
I know that this may sound stupid, but for what it's worth, I just wanna make sure.
Will my app still be considered Developer ID - signed if I exported it as a Mac Installer Package instead of selecting Export Developer ID-signed Application, when I install it to its destination devices? Will it be successfully installed or be rejected with GateKeeper-enabled devices?
I have been scratching my head for this since for some weird reason, I cannot add a new Distribution Developer-ID from the Dev Center. I was able to add a Developer ID earlier this week however, I ran into some issues with my private keys. As per suggested by Apple and many other developers, I revoked all the Developer IDs and private keys to start fresh. The problem now is that I can't add any new Developer ID (Distribution). I cannot add in both Dev Center and by requesting through Xcode 5.0.1. I'm stuck.
I have submitted a Bug Report to Apple, but who knows when they'll be able to resolve it.
So now, temporarily, since I don't have any choice (I guess), I'll use the Mac Installer Package, but the question is, will it work?
Any help would be very, very much appreciated.
I've done this recently and have created a third Xcode project configuration to Debug and Release called Archive, which is a copy of Release except the app is signed using the Mac App Distribution / Third Party Mac App Developer and, confusingly there is a third name used for this same certificate.
I then changed the Archive scheme to use the Archive configuration to build.
Before doing this I had errors on some Macs when signing with my Developer ID, in some cases they claimed the app was corrupted, and in other cases I got gatekeeper blocking the app, forcing me to override it in System Preferences > Security & Privacy.
I personally use xcodebuild (from Jenkins) to build the app for distribution to testers, which I package in a .dmg so they only need to drag it to /Applications or ~/Applications and I do all that using a script within the Jenkins configuration. Your experience may differ to mine if you are using the Xcode app instead.
On Xcode 4.2, I am trying to run my app on my iTouch (jailbroken on 4.2). The build succeeds however it ends automatically right after it succeeds without ever showing up on my device. I have already wen threw the prerequisites to run apps on my idevice without a dev account.
Devices left behind at 4.2.1 (armv6) are no longer supported in Xcode templates by default. There are a few hoops to jump through. This answer from MattyG sums it up nicely.
You didn't have an Apple Developer Account? You have to register for it and get the provisioning profile for development.
Pay the US$99 .
One of my coworkers set me up with a provisioning profile through our corporate profile. I have read through several tutorials and none of them corresponded to the steps he actually took to get it set up. In the end my device was listed under the devices section of the organizer with a green circle next to it (I am guessing that's good?) but when I try to run the application on my device I get the error I mentioned in the subject of this post. I should mention my device is jailbroken running iOS 4.2.6. Is the "jailbrokenness" of my device an issue?
This is like day one with Xcode and it is pretty overwhelming coming from the Linux command line and Emacs. I don't expect a complete walk through from any of you. But if you can point me to a nice long tutorial showing me how to set this up with the latest version of Xcode I would appreciate it.
Check if you can see your device in Organizer and verify iOS version installed on the device with the deployment target for your application. This is very often the case as you won't be able to deploy 4.3 application to 4.2.1 device (for example).
In Xcode Set the target to project_name | iOS Device
Then in Xcode From the product menu=>Build For=> Build For Testing