“We are unable to process your request”

NSURL *url = [NSURL URLWithString:s]; NSURLRequest *request = [NSURLRequest requestWithURL:url]; [_webView loadRequest:request];Somehow the request is getting converted from http to https in iOS 9 on iPad mini.In my shouldStartLoadWithRequest method, I log the requests and I notice that it starts okay with the requests being http, then it suddenly changes to https without me doing anything.Anyone seeing the same?

It seems third-party menu extras may finally be broken with El Capitan. iStat Menus disappeared and I can no longer install it. Console shows6/8/15 3:13:00.723 PM SystemUIServer[1012]: invalid menu extra: /Library/Application Support/iStat Menus 4/extras/iStatMenusDateAndTimes.menu6/8/15 3:13:00.723 PM SystemUIServer[1012]: unable to initialize menu extra /Library/Application Support/iStat Menus 4/extras/iStatMenusDateAndTimes.menuAnyone else experiencing this issue?

I cannot add any cards to Apple Pay. I get a message that says Could Not Add Card: Try again later or contact your card issuer for more information.I have tried with American Express, Mastercard, and Visa with same result, so I don't think card issuer is the issue.I did get e-mails from all of the above listed cards notifying me that the cards previously associated with iOS 8.4 had been deleted from my device, so it would at least appear that the cards are not somehow locked in the phone on the old setting. But I'm unable to add them back in.Any ideas?

Download and install ran smoothly, but my watch has now rebooted to a red exclamation point icon with a link to an Apple support page. I've tried restarting the watch by holding down the crown/button several times but my watch seems to be unable to boot past the exclamation point. What can I do?

I uploaded a new build to iTC and it has been in the processing state for several hours now. How long does this typically take?

My app supports Touch ID to allow the user to log in using a saved credential (password).When the user launches the app, they are immediately prompted to touch the home button to log in.A successful touch retrieves the credential and uses it to log in.We have been seeing sporadic problems under iOS 8.3.Upon launch the system will *not* prompt the user to touch, it will instead directly retrieve the correct credential and log in.I set the credential using the following code (some details shortened for readability):-(void)enrollTouchForUser:(NSString *)username { NSString *password = @passwordFromInterface; NSData *encodedPassword = [NSData encodePassword:password forUsername:username]; NSData *encryptionKeyData; // obtained from outside process - code not needed for this sample NSData *encryptedPassword = [NSData encryptDataWithKey:encryptionKeyData withData:encodedPassword]; // add the key to the keychain CFErrorRef error = NULL; SecAccessControlRef sacObject; // Should the secret be invalidated when

My install went about an hour to get the update started loading onto the watch. It then went through the first phase, did a full circle loop of the progress indicator, started that again and now is hanging at about 85% progress. The watch app indicated the software update was completed, at least as far as the configuration data is concerned.Would someone from Apple provide some concrete steps to take to either determine the watch is about the brick and I need to get it replaced, and then what I need to do to get it right with the next watch or to get this install to complete successfully.There is nothing quite like waiting 6 weeks to get the watch, using it for a whole week and a few days, and then being stuck unable to continue development.

This is mostly a heads-up to those looking to install the iOS9 beta - AirWatch Agent, for their MDM platform, crashes and can't execute under this beta.Awkward, but, beta is beta. Identifier: com.air-watch.agent Version: 5 (5.0.1) Code Type: ARM (Native) Parent Process: launchd [1] Date/Time: 2015-06-09 15:08:28.28 +1000 Launch Time: 2015-06-09 15:08:26.26 +1000 OS Version: iOS 9.0 (13A4254v) Report Version: 105 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000 Triggered by Thread: 0 Filtered syslog: None found Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 ??? 0000000000 0 + 0 1 AirWatch 0x0039a297 0xe0000 + 2859671 2 AirWatch 0x0033ddab 0xe0000 + 2481579 3 AirWatch 0x0033dcfd 0xe0000 + 2481405 4 AirWatch 0x0029add3 0xe0000 + 1813971 5 AirWatch 0x000e4e49 0xe0000 + 20041 6 libdyld.dylib 0x360629cf 0x3605d000 + 22991 Thread 0 crashed with ARM Thread State (32-bit): r0: 0x00000000 r1: 0x00000000 r2: 0x000f4240 r3: 0x00379ed

Hi All,I'm not sure if this is in the correct place since the new forums organisation, mods feel free to move if not.So i am Using AVFoundation to capture video and audio from an external device and to write to a ProRes encoded *.mov file.I started with an application that only writes video buffers to a file, and this works fine, producing a ProRes encoded .mov as expected.However when i add the Audio AssetWriterInput to the AssetWriter, the file that gets created appears to be invalid.I have checked all the return values for each step of the operation, and everything appears to be ok, it's not until i call finishWriting on the assetWriter at the very end of things that i get an error. Sadly checking this error reveals the -11800 AVErrorUnkown error, which isn't much help.Now, a few things to note- I am trying to create a file with multiple tracks of uncompressed audio. Eg 48Khz, 16-bit, however for the sake of simplicity currently my sample only uses 1 track, which means only 1 AVAssetWriterIput for the audi