Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
IOS Iphone Apple News

Apple Releases iOS 5 Beta 2 For Developers 72

Posted by timothy from the those-sneaky-developers dept.
BogenDorpher writes "Apple has just put up the second beta version of its new operating system for the iPhone, iPad, and iPod Touch devices. iOS 5 Beta 2 build 9A5248d is now available for registered iOS developers in the Apple Dev Center. iTunes 10.5 Beta 2 is also available for developers."
This discussion has been archived. No new comments can be posted.

Apple Releases iOS 5 Beta 2 For Developers More

Apple Releases iOS 5 Beta 2 For Developers

Comments Filter:

  • Release Notes (Score:4, Informative)

    by Anonymous Coward on Friday June 24, 2011 @08:12PM (#36563298)

    Notes and Known Issues

    The following issues relate to using the 5.0 SDK to develop code.
    Accounts

    When creating an iCloud account you can use any Apple ID provided it is a full email address and not a MobileMe account. If you have a MobileMe account, you can copy data from that account to an iCloud account to use during testing. You can find more information on iCloud at: http://developer.apple.com/icloud

    When setting up an iCloud or MobileMe account using the setup assistant and leaving Find My iPhone on, it might actually turn Find my iPhone off after the setup. Please verify in Settings/Mail, Contacts, Calendar/YourAccount that Find my iPhone is toggled On after leaving the setup assistant.

    There is a problem finding a device using Find My iPhone on the MobileMe website (www.me.com) when switching from iCloud back to MobileMe. To workaround this issue:

    On the device go to Settings->Mail, Contacts, Calendar->@me.com and Toggle Find My iPhone off and back on. Now the device should show up on MobileMe website.

    It is recommended that you disable Bookmarks on multiple accounts. If they are enabled, the results might be undefined.

    FIXED: When deleting a MobileMe account, an incorrect message is displayed on the device that says “This will delete all Photo Stream Photos from your device”. You can ignore this message.

    Address Book

    FIXED: Adding a CardDAV account of any kind (Yahoo, Address Book Server, etc) and then removing the account will result in the loss of the UI button to add a new contact. The button will not appear under Contacts App or the Contacts button under the Phone app.

    FIXED: Modifying the fields of an iCloud contact from an iOS device that was not the original source of the contact causes the contact’s photo to disappear on other iOS devices. The image is still there but it is not fetched properly.

    AirPlay

    Starting in iOS 5.0, video content in applications and websites are AirPlay-enabled by default.

    iOS 5.0 supports AirPlay of video via AV Foundation.

    The Apple TV screen saver may degrade mirroring performance over AirPlay. The screen saver can be disabled in Apple TV settings.

    Apple TV

    Apple TV Software beta enables users to mirror the contents of an iPad 2 to an Apple TV (2nd generation) using AirPlay. This beta software also enables Photo Stream on Apple TV so users can access photos stored in iCloud. Apple TV Software beta is being provided to test the latest AirPlay functionality with your iOS 5 apps and web sites. If you wish to install Apple TV Software beta on your device, you must first register your device UDID in the iOS Developer Program Portal.

    Assistant

    When signing in with a Classic MobileMe account via iOS 5.0 Setup Assistant, it offers iCloud Backup.

    Audio

    Using voice chat in iOS 5 requires setting the kAudioSessionMode_VoiceChat mode on the Audio Session, or setting the AVAudioSessionModeVoiceChat mode on the AVAudioSession object.

    In iOS 5 beta1, voice chat is currently not working on iPhone 3GS and iPod Touch 3rd generation devices.

    Bluetooth

    FIXED: When connected to Personal Hot Spot via Bluetooth, the internet connection for web browsing is not successful.

    CalDav

    FIXED: Despite turning off reminder sync with an iCloud account, editing in the reminders app displays the option to make a new reminder list under iCloud. By doing so, the list and to do items under the list will sync to other devices.

  • When I have errors in my code, or places in the code that produces warnings, I like my IDE to move the cursor to the actual line of code where the issue is.

    This used to work just fine in xcode 3, but I'll be damned if I can figure out how to replicate that behaviour in xcode 4. What I've always had to do is switch window panes to look at the error log, find the line number where the issue is, and then manually go there in that file.

    Seriously... I might as well just be using an ordinary text editor and

    • Re: (Score:1)

      by milas ( 988484 )

      Seriously... I might as well just be using an ordinary text editor and a command line compiler.

      But..but...that wouldn't require you to have the latest version of OS X (since XCode 4 is now distributed through the AppStore and dropped support for the 10.5 API), would leave you with over 4GB more of hard drive space (what's the point in having all that space if you're not going to use it?), and not require you to re-download the full installer every time there was a point upgrade!

      Why would you ever want THAT?

    • When I have errors in my code, or places in the code that produces warnings, I like my IDE to move the cursor to the actual line of code where the issue is.

      This used to work just fine in xcode 3, but I'll be damned if I can figure out how to replicate that behaviour in xcode 4. What I've always had to do is switch window panes to look at the error log, find the line number where the issue is, and then manually go there in that file.

      What's wrong with clicking the error / warning icon in the navigation pane? It shows me my warning, I click the warning and it shows the appropriate file with the offending line highlighted in yellow. Click the warning again, and it will pulse the warning highlight in your source again, no line hunting necessary.

      Is your complaint that Xcode just doesn't reposition your cursor? The highlight and caret where the warning occurs isn't enough?

      • Re: (Score:2)

        by mark-t ( 151149 )
        The behaviour you are describing is what I had always experienced with xcode 3. It seems to have stopped working that way for me with any new projects I created with xcode 4. Another poster above has given me some insight into what the problem may be, however... and I will test this more thoroughly when I get home tonight.

      • What's wrong with clicking the error / warning icon in the navigation pane?

        What's wrong is that it doesn't always work. If the source file is not in the project root directory, it won't do what you think it will. Instead, it will just open the source file at the top. Bugs filed, haven't seen it fixed in latest. Pain in the arse.

        • Re: (Score:2)

          by dgatwood ( 11270 )

          I've seen this bug, too, with the build-and-analyze stuff. I think the bug that mine was a dup of has been fixed already, so your problem might just go away in the Xcode build that came with this SDK beta.

          If it's still there, go back to your bugs and if you haven't already, attach a test project that reproduces the bug along with detailed steps to reproduce. That tends to make these sorts of problems a lot easier to find and fix. If it hasn't been fixed by now, that probably means that it only reproduces

    • Re: (Score:2)

      by Trillan ( 597339 )

      There's a couple minor bugs that can cause this. Are you using the latest released Xcode 4? At least one of the causes was fixed in a .0.1 release.

      Other than that, search StackOverflow, etc.

      Important thing to know is that your experience isn't typical. There IS a fix. Sorry I can't give you details; I haven't run into this myself, but discussed in passing with someone who had hit it.

      • Re: (Score:2)

        by mark-t ( 151149 )
        It has been pointed out to me that the problem may have been getting caused by the fact that it happens to be the case that all of my newer projects do not have the source files underneath the project folder, because this produces the exact same behaviour when there are errors or warnings in the files as what I experienced.

      • Important thing to know is that your experience isn't typical.

        His experience absolutely is typical, in that he has experienced inexplicable, infuriating and inconsistent behaviour from Xcode. Xcode 3 was never great, but 4.x is beta software, which has been rushed out the door without proper quality testing, and as of 4.2, still has serious issues (not just this one). I upgraded a few weeks ago to 4.0.2 as I saw it was now the official release version of Xcode, and am now realising that was a serious mistake. Just as one example, opening the archives window causes hug

        • Re: (Score:2)

          by Trillan ( 597339 )

          You're kidding right? Only a few releases ago, Xcode 3 produced code that hard crashed on armv6. A few months before that, it produced code that potentially crashed on startup, but only when re-signed by Apple's keys.

          I can't remember the last time I fought code signing problems for a full day, but I can assure you it was with Xcode 3 not 4.

          This is the way it is, and if anything it's getting better as time goes on.

    • Comment removed based on user account deletion

  • more than 2 developers, no? Sounds stingy.

  • ...and even I'm having trouble caring about this. It's one thing when they talk about it on the Mac news and rumors sites I go to, but here too? Come on. They've already announced it, so it's not like we're getting a sneak peek of some forbidden information. The features are already known, nothing newsworthy has been discovered yet, and it's not available to the public, but will be soon. Its release will be newsworthy in a few months, but the release of a beta build of it that's only for developers and does

    • ...and even I'm having trouble caring about this. It's one thing when they talk about it on the Mac news and rumors sites I go to, but here too? Come on. They've already announced it, so it's not like we're getting a sneak peek of some forbidden information. The features are already known, nothing newsworthy has been discovered yet, and it's not available to the public, but will be soon. Its release will be newsworthy in a few months, but the release of a beta build of it that's only for developers and doesn't change much, let alone signal when a potential release date might be? No.

      So, your interest level is so low, that you felt compelled to click on the story just to bitch about its very existence?

      Pro tip: When encountering a headline for a story for which you have little to no interest, simply direct your attention to other stories. That way, you won't feel compelled to bitch about the story that you didn't care about, thus polluting slashdot's database with even more useless infromation, with your useless comments about useless (to you) information.

      Or are you just trying to ma

      • I find it rich that a guy who posted a 6-point list of grievances against Slashdot [slashdot.org] is trying to tell me off for listing a single one. I typically do follow your advice and simply ignore stories I don't want to read, but when an article isn't "stuff that matters", I don't see a problem in people pointing it out (though I typically do not do so myself).

    • Re: (Score:1)

      by gl4ss ( 559668 )
      the changelog upward is worth a look. you know, for real dirt and not just marketing shit which we know already can be just marketing shit since this is consumer computers we're talking about.
  • Comment removed based on user account deletion
  • ... I cannot text, mail, and make any call anymore but boy that paradigm shift a game changer! Don't forget this is a .0 release you trolls.

Slashdot Top Deals

Your password is pitifully obvious.

Close