“DTiPhoneSimulatorErrorDomain Code 2”

Problems updating to Watch OS 2 BETA 2. I have downloaded the Config Profile on both my iPhone and Apple Watch. Restarted both and everytime I check for an update it says it is up to date. Any suggestions or work arrounds for this issue? iPhone is running ios 9 beta 2 and watch is running watch os beta 1.

The only things I can find about sending HTTP/2 push notifications show using libcurl inside of PHP. That will work, but the docs pretty clearly say to keep a connection open, and using curl like this does not do that. The Apple documents are ridiculously lacking in how to make an HTTP/2 connection.Has anybody figured out how to upgrade their server side code to deal with HTTP/2 properly?

Installed the Watch OS 2 Beta 2 after it was re-introduced today. However, the build showed up 2.0 (13S5255d). Apple's Dev SDK states it should be 13S5255c. What build do you have?

can i use a single UITableViewDiffableDataSource with two table views at the same time or is it not supported? traditional datasources can do that, and my code has this dependency at the moment.

Hi everybody,I just installed the watchos 2 beta 2 on my Apple Watch.After the installation was complete, my Apple Watch rebooted, the clock shown up... but then after few seconds, a loading screen with the apple in the center appeared. Since that, nothing moves...If I try to reboot the Apple Watch manually, it's the same : that loading screen shows up after a fews seconds and the Apple Watch looks totally blocked.Any Idea ? How to get back to the watchos 1 version with my Apple Watch broke, ?Thanks a lot in advance,

I’m implementing a subscription purchase flow using promo code redemption via an external App Store URL. Flow: User taps “Purchase” in the app (spinner shown) App opens the promo redemption URL (apps.apple.com/redeem) User completes redemption in the App Store User returns to the app The app must determine whether the subscription was purchased within a reasonable time window The app listens to Transaction.updates and also checks Transaction.currentEntitlements when the app returns to the foreground. Issue: After redeeming a subscription promo code via the App Store and returning to the app, the app cannot reliably determine whether the subscription was successfully purchased within a short, user-acceptable time window. In many cases, neither Transaction.updates nor Transaction.currentEntitlements reflects the newly redeemed subscription immediately after returning to the app. The entitlement may appear only after a significant delay, or not within a 60-second timeout at all, even though the

Hello i have this problem, I have to concatenate two textfield in this , so you getEmail=pippo@gmail.com&Password=3844893I used this code but does not worklet postString = Email= +Email.text+&Password=+Password.textCan you help me?

I have encountered this error while using service.generateAssertion. But I am not understanding what does this error mean exactly.

In Pure Swift environment (no briding to NSArray)Problem: [[1]]==[[1]] //false or ([[1]] as Array)==([[1]] as Array) //false This problem only happens in pure Swift environment.Though [1] == [1], any array of integers is not marked equatable. Programmer cannot mark [Int], [String], …, etc. as Equatable protocol.Thus two [[Int]] cannot be compared using “==“.Solution 1: extension SequenceType: Equatable where Generator.Element: Equatable { }This gramma should be allowed in newer version of Swift.This means a SequenceType with Equatable elements can be marked Equatable.Solution 2:You can make a new mechanism in Swift that automatically binds “Equatable” to any generic type has “==“ operator defined.For example, in Swift Standard Swift Library, you have defined==<T: Equatable>(lhs:[T], rhs:[T])->BoolThus, the special generic type [T] where T:Equatableshould be automatically marked as “Equatable.

Hello Apple Developer Support Team, I am the Account Holder of my Apple Developer Program team (Team ID: T2BKUF6E93). My iOS app is using Swift WeatherKit (WeatherService) on device. Although my environment is completely configured, the system WeatherDaemon consistently fails to generate the WeatherKit JWT token. My environment: Team type: Apple Developer Program (paid) Team ID: T2BKUF6E93 Account role: Account Holder Xcode: latest version Device: iPhone (real device) Provisioning Profile: iOS Team Provisioning Profile (auto-managed) Entitlement: com.apple.developer.weatherkit included WeatherKit Key: created successfully (.p8 downloaded) Bundle ID: correct and WeatherKit capability enabled App reinstalled after each configuration change Device rebooted Even after enabling WeatherKit capability and generating a WeatherKit Key, the system still fails to generate JWT: Failed to generate jwt token for: com.apple.weatherkit.authservice Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code

Haven't been able to test this yet, but does multi room support with Airplay 2 work on two apple TVs running tvOS 11.By this I mean can you use Airplay 2 to play a song on one apple tv and a different song on another?Thanks

I have been trying to figure this out for like 5 hours, and I can't seem to see what its happening. My app is trying to get users signIn with using Google or Apple methods. Once they finish the SignUp with any provider, It should take them to another screen (OnboardingViewPart2) to finish the profile setup. However, the issue is that when I finish entering my email on the Google SignUp, the screen closes and the app get stuck for like 10 secs and throws the Bad Access error. My debug takes me that there is something going on with AuthService, but I can't figure out what. Firebase recognizes that the method was used, but doesn't create any Collections or Documents. Please Help :) ContentView.swift OnboardingView.swift AuthService.swift OnboardingViewPart2.swift SignInWithGoogle.swift

Hi all,I've 2 separate conversations with 2 different contacts (not the same phone number, nothing in commun).On my MacBook (High Sierra) everything works fine.But on my iPhone X running iOS 12 beta 3 (since beta 2 I've this bug), these 2 conversations are merged.When I write to one or another of these 2 contacts, it displays the 2 conversations in one screen. It merges them.When I try to create a new message, when I enter one of the 2 contacts, I don't know who receive the message, it's not always the same one that receive the message.That's really annoying.Does anyone have this issue too?I filled a bug reporter for that.Regards,Alexandre