beta

I'm planning to release a beta version of my iPhone app on iOS 8 devices through the new Apple TestFlight app. What kind of Certifcate and Provisioning Profile is needed for that? Do I need a Production certificate and Distribution provisioning profile? Available are these: Certificate: - Pending - Development - Production Provisioning Profile: - Development - Distribution I believe you need a Production certificate with a Distribution profile for "App Store". I just submit my app which is now in review for external beta testers. The first time I submit the app I was using an Ad Hoc profile as

Im using the Microsoft Graph to get calendar event with application permission. It works perfectly. Now Im trying to set up a subscription to listen to event changes however the normal v1.0 do not suport this. However beta, at least in the description, say it works. From the page: https://graph.microsoft.io/en-us/docs/api-reference/beta/api/subscription_post_subscriptions "Note: the /beta endpoint allows Application permissions as a preview feature for most resources." So I tried this with the URL: https://graph.microsoft.com/beta/subscriptions Sending in a json object like this: { "changeType

Is it just me who experiences the whole scene freezing in ARKit on iOS 12? It usually happens when you use the app for too long in a space that generates too dense point cloud. After certain amount of time, the whole picture starts to lag and then would stop moving at all, until you cover the camera, or turn it away from your objects, or reset AR session. Since I have updated to iOS 12, I started to experience this issue, but I searched a few forums to see if someone else got this problem and couldn’t find anyone. I wonder if it’s just me, or is it a common bug? UPD: iOS 12 beta 2 - the issue

I am receiving and error when trying to build, Xcode 8.0 Beta 4, and when I'm building it says "error: Illegal Configuration: Key Commands must all have a Title, Key, and Selector. Select each row in the table to check its configuration." It isn't on a TableView or anything, its a UIView with a Stack View inside it and some buttons, thats about it. And this is on a Storyboard file I'm getting the error I can't figure out what that might be? Open your storyboard file as source code (right click -> open as -> source code). There should be a line, <keyCommands> <keyCommand/> </keyCommands> .

I noticed that there are no preview or simulator for iOS6 in Xcode 6-beta, so I was wondering is there any way that I could add it manually ? No. Apple only support iOS7 and iOS8, and they're strict with that. As a result, only iOS7/8 simulators are available in Xcode 6. If you want to run on an older simulator, you need to develop on an older version of XCode. Not possible. But: you can still test on a iOS 6 device from Xcode 6. I keep an old iPhone 4 for this (look at eBay). EDIT: there is another way - install Xcode 5 on a virtual machine (e.g. VMWare Fusion) running Mavericks. iOS6

Are the new notifications not currently working in Swift 3? I am doing: NotificationCenter.default().post(name: DidTouchParticleView, object: self.particle as? AnyObject) In a custom view's touchesBegan() and I need to send the particle object to the view controller if there is one. So I do this: NotificationCenter.default().addObserver(forName: DidTouchParticleView, object: self, queue: OperationQueue.main(), using: presentParticleDisplayView(notification:)) In a view controller's viewDidLoad() . I am certain that that particular view controller is the one presented when I tap my custom view,

I distributed version 1.0, build 1, of my app via TestFlight, and everything worked perfectly. Yesterday I archived and sent out build 2, and now upon tapping the update button, every user seems to be getting an error: Unable to Download App [App name] could not be installed at this time I haven't heard from any users who didn't have build 1 installed already, but looking at iTunes Connect, no user has build 2 installed. I've got this error many times, but I saw a really strange pattern and I have a pretty weird theory. Next time, after you submit your app to Apple, don't submit it immediately