A Summary of the WWDC25 Group Lab

Same in XCode 6.1 and ios 8.4. Some users advice to set up App Groups, however it doesn't help. Anyway, everyting works fine. Maybe that's a bug of XCode?

Still not working in 7b5.Hmmm - just read the Xcode 7b5 release notes. I see this:NetworkingNoteWhen negotiating a TLS/SSL connection with Diffie-Hellman key exchange, iOS 9 requires a 1024-bit group or larger. These connections include:Secure Web (HTTPS) ...Now, my forwared cipher is ECDHE_RSA_WITH_AES_128_CBC_SHA - hmmm - is DHE in that name stand for Diffie-Hellman [key] Exchange?So the next question is - is the above a note on a limitation, or an announcement of what the future holds?NOTE: there is this tidbit too - not sure if related or not:Secure TransportNoteDHE_RSA ciphersuites are now disabled by default in Secure Transport for TLS clients. This may cause failure to connect to TLS servers that only support DHE_RSA cipher suites. Applications that explicitly enable ciphersuites usingSSLSetEnabledCiphers() are not affected and will still use DHE_RSA ciphersuites if explicetely enabled.

okay set the date, but the log was from before, however, everything at this time was what I just did now:sorry for copying everything but might as well go back wo what i did just now, in case something stands out and not too sure what to look for since Mac is BSD based and I am not too versed in that flavour (in fact I tried copiling GNU coreutil to make some of my shell scripts I did work better (mainly with switches)). I just hate how it is /Users and not /home (i did make a symlink though lol)Jan 3 22:04:46 localhost bootlog[0]: BOOT_TIME 1420340686 0 Jan 3 22:04:48 localhost syslogd[48]: Configuration Notice: ASL Module com.apple.AccountPolicyHelper claims selected messages. Those messages may not appear in standard system log files or in the ASL database. Jan 3 22:04:48 localhost syslogd[48]: Configuration Notice: ASL Module com.apple.Accounts claims selected messages. Those messages may not appear in standard system log files or in the ASL database. Jan 3 22:04:48 --- last message repeated 1 time --- Ja

Part 2:ASL Module com.apple.securityd claims selected messages. Those messages may not appear in standard system log files or in the ASL database. Jan 3 22:04:48 --- last message repeated 7 times --- Jan 3 22:04:48 localhost syslogd[48]: Configuration Notice: ASL Module com.apple.server.servermgrd.log claims selected messages. Those messages may not appear in standard system log files or in the ASL database. Jan 3 22:04:48 --- last message repeated 5 times --- Jan 3 22:04:48 localhost syslogd[48]: Configuration Notice: ASL Module com.apple.serverdocs claims selected messages. Those messages may not appear in standard system log files or in the ASL database. Jan 3 22:04:48 localhost syslogd[48]: Configuration Notice: ASL Module com.apple.servermetricsd claims selected messages. Those messages may not appear in standard system log files or in the ASL database. Jan 3 22:04:48 localhost syslogd[48]: Configuration Notice: ASL Module com.apple.xpc.activity claims selected messages. Those messages may not appear in

Thanks for the response Joar,Continuous-integration servers (especially those which run as Infrastructure-as-a-service models like Travis, Cloudbees, CircleCI, Sauce Labs) aren't usually trusted with full Xcode project files.Right now we use the Instruments commandline tool to run tests on a developer build of the app. This way, the only artifact required for testing is a compiled app file (with developer permissions).Wouldn't xcodebuild require the full source of the app, the entire project file?Appium tests specifically live outside of a developer's app, and are communicated via http to the appium server. How we would like to handle this is by building a standard appium xcuitest which is essentially a web server that waits for http commands and dynamically runs tests on the device. We've already experimented with building an xcuitest app for any given iOS app, but the exact sequence to kick-off the testing process on the device is not currently accessible to us.Not sure if you've heard of Appium. I

Having seen a client do this via transfering their app to another developer, I can point out unless you had a group related identifier for the keychain, you then lose access to the keychain data. For this particular client that resulted in every customer who updated their app had to reenter their login credentials and settings as that was all stored in the keychain.