Showing posts with label redsn0w. Show all posts
Showing posts with label redsn0w. Show all posts
Friday, October 11, 2013
Redsn0w 0 9 6rc11 Ramdisk Freezing Errors 4 3 1 Fixed
You may be you faced some errors like freezing, uploading ramdisk or etc while jailbreaking your iPhone, iPad or iPod touch on the latest iOS 4.3.1 firmware redsn0w 0.9.6rc11 untethered jailbreak. The below embedded video will help you to fix these errors.
How to Jailbreak 4.3.1 Untethered Redsn0w 0.9.6rc9 iPhone 4, 3G /iPod Touch 4G, 3G / iPad [Guide]
iOS 4.3.1 untethered jailbreak has just been released few minutes ago for both Redsn0w 0.9.6rc9 and PwnageTool 4.3, the jailbreak support all iOS devices except iPad 2. You can follow the below guide to get untethered jailbreak for your iOS device.
NOTE: Users who rely on ultrasn0w unlock MUST stay away from Redsn0w.
Step 1: Download iOS 4.3.1 for your device (download links at the end)
Step 2: Update/Restore to iOS 4.3.1 firmware using the IPSW file via iTunes 10.2.1.
Step 3: Start Redsn0w and point it to the official iOS 4.3.1 firmware file.
Step 4: Now simply select “Install Cydia” and click “Next”.
Step 5: Now make sure your device is both OFF and PLUGGED IN to the computer before you click “Next”.
At this stage you will be presented with a screen where you will be guided on how to enter DFU mode. Quickly hold “Power” button and then while holding the “Power” button, you will now have to hold “Home” button too. Now after few seconds release “Power” button but keep holding “Home” button until installation begins.
Step 6: Wait shortly. Once done, your iPhone, iPad or iPod touch will restart automatically and you will find it fully jailbroken (untethered) on the latest iOS 4.3.1 firmware.
Download Redsn0w 0.9.6rc9 (Windows)
Download Redsn0w 0.9.6rc9 (Mac)
Download iOS 4.3.1 for all iPhone, iPod touch, iPad and Apple TV 2G
Heres the direct download links:
Read more...
How to Jailbreak 4.3.1 Untethered Redsn0w 0.9.6rc9 iPhone 4, 3G /iPod Touch 4G, 3G / iPad [Guide]
iOS 4.3.1 untethered jailbreak has just been released few minutes ago for both Redsn0w 0.9.6rc9 and PwnageTool 4.3, the jailbreak support all iOS devices except iPad 2. You can follow the below guide to get untethered jailbreak for your iOS device.
NOTE: Users who rely on ultrasn0w unlock MUST stay away from Redsn0w.
Step 2: Update/Restore to iOS 4.3.1 firmware using the IPSW file via iTunes 10.2.1.
Step 3: Start Redsn0w and point it to the official iOS 4.3.1 firmware file.
Download Redsn0w 0.9.6rc9 (Windows)
Download Redsn0w 0.9.6rc9 (Mac)
Download iOS 4.3.1 for all iPhone, iPod touch, iPad and Apple TV 2G
Heres the direct download links:
- iPhone 4
- iPhone 3GS
- iPad 2
- iPad
- iPod touch 3G
- iPod touch 4G
Download iTunes 10.2.1 for Windows / Mac OS X
Sunday, October 6, 2013
Jailbreak 4 3 5 iPhone 4 3GS iPod Touch 4G 3G iPad with Redsn0w
As you know that Apple has released iOS 4.3.5 to fix security issue. The good news is that some guys have confirmed that current Redsn0w version can jailbreak 4.3.5 iPhone 4, 3GS, iPod Touch 4G, 3G, iPad 1.
As we reported you that this jailbreak is still tethered jailbreak which means that you will need to reconnect your iDevice with computer every time your reboot iDevice.
[h=2]Jailbreak 4.3.5 iPhone 4, 3GS, iPod Touch 4G, 3G, iPad:[/h]Step 1: Download iOS 4.3.5 and iOS 4.3.4 (required by this version of Redsn0w) firmware file for your device from the links given at the end.
Step 2: Download Redsn0w 0.9.8b4 for Windows or Mac. Also make sure you are running the latest version of iTunes, which is version 10.4.
Step 3: Now start Redsn0w, browse for the iOS 4.3.4 firmware file (NOT the 4.3.5) that you downloaded in Step 1 and point it towards Redsn0w. Refer to the screenshots below:
Step 4: Once Redsn0w is done recognizing the firmware file, click Next and there you’ll be taken to a new window. Simply check the “Install Cydia” box as shown below and leave other options as it is for now. Once done, click Next.
Step 5: On this screen, Redsn0w will instruct you to power down your device and plug it in to your computer. Follow the onscreen instructions and then click Next to continue.
Step 6: On this screen you will have to put your device in DFU mode with a combination of the Power button and the Home button for a certain amount of time, simply follow the onscreen instructions on how to do so. The combination is usually like this:If you performed the above mentioned steps correctly, then your device should be in DFU mode.
- Hold down Power button for 5 seconds.
- Now without releasing the Power button, hold down the Home button simultaneously with the Power button for 10 seconds.
- Let go of the Power button but keep on holding the Home button for another 15 seconds.
Step 7: Redsn0w will now jailbreak your device, don’t do anything weird at this point, just let Redsn0w finish. We would recommend that you don’t do anything with your PC or Mac at all during the process. Sitting idle and waiting for the process to end on its own is much advised.
Since this is a tethered jailbreak, therefore whenever your iOS device loses power, it will go into the dreaded Apple logo boot screen loop. To get out of that, simply start from Step 3 again and in Step 4, uncheck “Install Cydia” and instead check “Just boot tethered right now” option and hit “Next” with your iPhone, iPad or iPod touch connected to your PC or Mac. And yes, you will have to do this every time when your device reboots or loses power.
That’s it! You should now have a jailbroken iPhone, iPad, or iPod touch running iOS 4.3.5.
Saturday, October 5, 2013
Jailbreak iOS 4 3 1 Untethered with Redsn0w 0 9 6rc9 for iPhone iPod Touch iPad How to Guide
Few minutes ago Dev-Team has released iOS 4.3.1 untethered jailbreak for both Redsn0w 0.9.6rc9 and PwnageTool 4.3, the jailbreak support all iOS devices except iPad 2
NOTE: Users who rely on ultrasn0w unlock MUST stay away from Redsn0w.
Step 1: Download iOS 4.3.1 for your device (download links at the end)
Step 2: Update/Restore to iOS 4.3.1 firmware using the IPSW file via iTunes 10.2.1.
Step 3: Start Redsn0w and point it to the official iOS 4.3.1 firmware file.
Step 4: Now simply select “Install Cydia” and click “Next”.
Step 5: Now make sure your device is both OFF and PLUGGED IN to the computer before you click “Next”.
At this stage you will be presented with a screen where you will be guided on how to enter DFU mode. Quickly hold “Power” button and then while holding the “Power” button, you will now have to hold “Home” button too. Now after few seconds release “Power” button but keep holding “Home” button until installation begins.
Step 6: Wait shortly. Once done, your iPhone, iPad or iPod touch will restart automatically and you will find it fully jailbroken (untethered) on the latest iOS 4.3.1 firmware.
Download Redsn0w 0.9.6rc9 (Windows)
Download Redsn0w 0.9.6rc9 (Mac)
Download iOS 4.3.1 for iPhone, iPad and iPod touch
Download iTunes 10.2.1 for Windows / Mac OS X
Read more...
NOTE: Users who rely on ultrasn0w unlock MUST stay away from Redsn0w.
Step 2: Update/Restore to iOS 4.3.1 firmware using the IPSW file via iTunes 10.2.1.
Step 3: Start Redsn0w and point it to the official iOS 4.3.1 firmware file.
Download Redsn0w 0.9.6rc9 (Windows)
Download Redsn0w 0.9.6rc9 (Mac)
Download iOS 4.3.1 for iPhone, iPad and iPod touch
Download iTunes 10.2.1 for Windows / Mac OS X
Downgrade your iPhone 4S iPad 2 or new iPad with RedSn0w 0 9 11b1
It’s finally here folks, the official downgrade tool for A5 devices!
Starting with redsn0w version 0.9.11b1, those with newer devices (iPad2, iPad3, and iPhone4S) can join the downgrade fun too!
In a radical departure from previous versions of redsn0w, it now directly supports restoring IPSWs to your device. The first use of this new feature implements a hack that allows A5 downgrades without a bootrom-level exploit.
Indeed, you can now downgrade your iPhone 4S, iPad 2, or new iPad (iPad 3) with the latest version of RedSn0w 0.9.11b1. Downgrading will allow you to perform an untethered jailbreak on your iPhone 4S, or iPad 2 running iOS 5.0.1 firmware.
Check out our tutorial for the step-by-step downgrade instructions inside…
Note: You must have your SHSH blobs for iOS 5.0.1 either stored locally by means of TinyUmbrella, etc., or Cydia must have your 5.0.1 blobs for this downgrade to work successfully.
Step 1: Download the latest version of RedSn0w 0.9.11b1 RedSn0w 0.9.11 beta 1: Mac • Windows
Step 2: Download the latest firmware (5.1.1) for your device from our downloads page, along with the 5.0.1 firmware.
Step 3: Place your device into DFU mode.
Step 4: Run RedSn0w 0.9.11b1, and make sure RedSn0w detects your device in DFU mode. Navigate to Extras > Even more > Restore and click IPSW under the IPSW section. RedSn0w will then ask you for your iOS 5.0.1 IPSW. Once you locate iOS 5.0.1, RedSn0w will ask your for the latest firmware (iOS 5.1.1).Step 5: Once both firmwares have been validated, it’s time to locate your saved SHSH blobs. If you’ve jailbroken your device before, you should have those available on Cydia, and therefore you can use the Remote option. If you’ve never jailbroken your device before, but you saved your SHSH blobs with a tool like TinyUmbrella, then choose Local and browse your computer for your blobs. We’d recommend clicking the Remote option first.Step 6: Once your blobs have been verified, there is nothing left for you to do, just let RedSn0w execute the full process. First RedSn0w will install a hacked version of the latest firmware (iOS 5.1.1), and then it will downgrade your firmware to iOS 5.0.1.
Step 7: Upon downgrading successfully you will be presented with a success message. Now all you have to do is setup your device, and verify that you are now on iOS 5.0.1 via Settings > General > About on your device.What’s Next?
Most people will want to jailbreak their newly downgraded device. If you’re using an A5 device like the iPad 2, or iPhone 4S, you can now jailbreak using Corona-A5. You can do this directly from RedSn0w. We will have a tutorial that shows you how to jailbreak your A5 device using RedSn0w in the near future. Until then, you can always use a tool like Absinthe Absinthe v0.4: Mac - Windows - Linux to jailbreak as well.
Were you able to downgrade successfully? Have any tips or tricks? Please share them below!
Important: If you rely on a software unlock or SIM interposer for your iPhone, beware! This method will update your baseband, and you could permanently lose your unlock.
UPDATE
5x redux
What’s old is new again!
Jailbreakers with devices that pre-date the iPad2 will always be able to downgrade (with SHSH blobs) to previous firmware versions due to geohot’s limera1n exploit, which allows us to bypass the restrictions that Apple places on restores. But until now, that ability has been limited to those older devices (if you have an older device and don’t know how to do that, check the popular tutorial sites or ask in the comments below).
Starting with redsn0w version 0.9.11b1, those with newer devices (iPad2, iPad3, and iPhone4S) can join the downgrade fun too! In a radical departure from previous versions of redsn0w, it now directly supports restoring IPSWs to your device. The first use of this new feature implements a hack that allows A5 downgrades without a bootrom-level exploit.
Some important points:
- The new feature is at Extras->Even More->Restore
- You cannot downgrade without the personalized SHSH blobs for your device at that lower firmware. You need to have fetched those blobs while the signing window was open, using either Cydia’s built-in TSS@Home feature, or with TinyUmbrella. The new Restore screen of redsn0w lets you choose either the remote blobs or local ones (for the earlier firmware). If you don’t know where TinyUmbrella put your blobs, TinyUmbrella has a button that will show you (copy them out of that folder and feed them to redsn0w).
- The A5 downgrade method actually updates to the latest firmware before downgrading to the earlier one. This process updates your baseband to whatever is newest. DO NOT USE THIS METHOD IF YOU RELY ON UNOFFICIAL UNLOCKS of your iPhone4S. Those who used the temporary SAM technique to unlock their iPhones to specific SIMs shouldn’t be affected by this baseband update.
- This method can be fixed by Apple with a firmware update. It’s a (pleasant) mystery why they haven’t fixed it yet, because reverse-engineering of the restore ramdisk indicates they do know about it. It’s possibly too niche to bother to fix right now.
- The least-tested devices with this method are the iPad2,3 and iPad3,2 (because we don’t have those models). If you do and you feel like experimenting, please let us know how it turns out in the comment section below!
- This update involves a bunch of new redsn0w code. We recommend sticking to the previous version 0.9.10b8b unless you’re specifically using this new feature, until all the bugs are worked out! (Note: If redsn0w gets stuck at the “Waiting for device” stage for more than 30 seconds, you’ve hit a pesky GUI bug…that will be fixed in an upcoming version!)
Of course all eyes are on @pod2g for his upcoming 5.1 untethered jailbreak. Watch his blog or twitter feed for the latest updates about that, but in the meantime if you accidentally updated your jailbroken A5 device to something later than 5.0.1, feel free to try this new A5 firmware downgrade feature of redsn0w!
Update #1: We accidentally left out one of the two flavors (“9A406”) of 5.0.1 for iPhone4S. It’ll be in the next update, but in the meantime check if Cydia or TU saved your blobs for the other 5.0.1 for iPhone4S (“9A405”). Version 0.9.11b2 adds support for that second “9A406” flavor of 5.0.1 for the iPhone4S.
Update #2: Version 0.9.11b3 should fix the spurious “Restore failed” messages people were sometimes getting, and it behaves better with nearby devices that have wifi syncing enabled!
Update #3: Version 0.9.11b4 completes the tethered JB support for 5.1.1 on A4 devices and earlier, including proper “Stitching” and “Custom” creation of NO_BB IPSWs.
Here are the redns0w download links:
- redsn0w 0.9.11b4 for OS X
- redsn0w 0.9.11b4 for Windows (be sure to run in Administrator mode)
Sunday, September 29, 2013
Jailbreak iOS 5 beta 3 iPhone iPod Touch iPad Redsn0w Caution
Jailbreak iOS 5 beta 3 - iPhone, iPod Touch, iPad - Redsn0w
Today the new Beta version of iOS 5 has been released named as iOS5 Beta 3. now there is need for most of the users of this new version of firmware to jailbreak their devices. There is good news for those that they can easily jailbreak the latest version of iOS 5 beta 3. There is no tool updated for the jailbreak, but the last version of Redsn0w that was released to jailbreak iOS 5 Beta 2 can jailbreak iOS Beta 3 as well. But this new version and jailbreak is only for developers. Here is the announcement made by MuscleNerd about the jailbreaking of new firmware.iOS 5 Beta 3 Can Be Jailbroken Using Redsn0w 0.9.8b1; But App Store Apps Are Not WorkingThis jailbreak method is same as was in the past for Redsn0w by putting the device in DFU mode, but remember this jailbreak is also tethered.
Here is a bit guide about jailbreaking new version iOS 5 Beta 3. first update you iDevice with this latest firmware via iTunes. Then you need to run Redsn0w 0.9.8 and select the firmware iOS 5.0 beta1. if you select other firmware then you will not be able to jailbreak your device running iOS Beta3.
Again this is tethered jailbreak, it means that every time you switch off your device, you will have to connect it to your PC and use the option “Just boot tethered right now” to use your device.
iOS 5 beta 3 that has just been seeded to developers of iOS developer program can be jailbroken using Redsn0w 0.9.8b1.iPhone Dev team had released Redsn0w 0.9.8b1 for Mac and Windows for iOS beta 1 for developers of jailbreak app developers so that they can test and debug their jailbreak apps and tweaks on iOS 5.After upgrading your iOS device to iOS 5 beta, the trick is to point Redsn0w 0.9.8b1 to iOS 5 beta 1 firmware file to jailbreak it.MuscleNerd of the iPhone Dev Team has also confirmed this on Twitter:
Todays 5.0b3 can be jailbroken with last months redsn0w http://is.gd/6eek4Y (point it at 5.0b1 IPSW..devs only please!)
But please proceed with caution if you’re not a jailbreak app developer as we’re hearing reports that App Store apps do not working after jailbreaking iOS 5 beta 3. ModMyI reports: After playing around on iOS 5 beta 3 while jailbroken, it has been discovered that AppStore applications do not work. They crash and refuse to open. It is an issue that has been reported by a few people, including myself.
According to hacker, Clayton Braasch it is due to a sandboxing issue: To reiterate: theres a sandbox issue causing App Store apps to crash after jailbreaking iOS 5 beta 3. Stay away if youre not a developer.
It needs to be seen if this is due to some anti-jailbreaking measure introduced by Apple in the latest iOS 5 beta. Wednesday, September 25, 2013
Redsn0w 0 9 8b7 Released With Added Support To Updated iPad iOS 5 Beta 6 IPSW
A new release of Redsn0w has just been released with added support for the updates ipsw file for iPad 1 iOS 5 Beta 6.
MuscleNerd has posted the new on his twitter account. This minor update comes after Apple updating the IPSW for the iPad 1 on iOS 5 Beta 6 But they didn’t change the version number or the file name for unknown reasons.
This update of Redsn0w can jailbreak both th original and the updated ipsw. Also this update supports iOS 4.3.5 and iOS 4.2.10 which means you won’t have to point Redsn0w to IPSWs of iOS 4.3.4/4.2.9 when using it to jailbreak your device.Update #7: Apple updated the iPad1 iOS5b6 IPSW without changing its version number or filename, so we’re releasing redsn0w 0.9.8b7 to handle both the original and changed IPSW. We’ve also added explicit support for a tethered 4.3.5/4.2.10 jailbreak (instead of pointing at the 4.3.4/4.2.9 IPSWs) and fixed a 4.2.10 problem.Here is how to use Redsn0w to jailbreak your device[Tutorial].
Download Redsn0w 0.9.8b7 For [Mac & Windows].
Tuesday, September 17, 2013
Redsn0w 0 9 8b7 Can Jailbreak iOS and 5 Beta 7 Download Links Here!
Yesterday, Apple has seeded iOS 5 Beta 7 for developers. Many would now be looking for a jailbreak for the new update. Well MuscleNerd has announced on his twitter account that the just released Redsn0w 09.8b7 can jailbreak iOS 5 Beta 7.
Of course you will have to point Redsn0w to iOS 5 Beta 6 IPSW firmware not the new one.
Here is our tutorial on how to use Redsn0w To Jailbreak iOS 5 Beta 1 and you can follow the same steps for Beta 7.
Download Redsn0w 0.9.8b7 For Windows / Mac
Apple releases iOS 5 Beta 7 Download Links Here!
Of course you will have to point Redsn0w to iOS 5 Beta 6 IPSW firmware not the new one.
Here is our tutorial on how to use Redsn0w To Jailbreak iOS 5 Beta 1 and you can follow the same steps for Beta 7.
Download Redsn0w 0.9.8b7 For Windows / Mac
Apple releases iOS 5 Beta 7 Download Links Here!
DMG Links:
iPad 2 WiFi + 3G (GSM)
iPad 2 WiFi + 3G (CDMA)
iPad (WiFi and WiFi + 3G)
iPhone 4 (GSM)
iPhone 4 (CDMA)
iPhone 3GS
iPod Touch (3rd Generation)
iPod Touch (4th Generation)
AppleTV
IPSW Links:
iMZDL: iOS 5 & Mac OS X 10.7
iTunes 10.5Beta7
Apple Mac OS X
Microsoft Windows
Microsoft Windows 64-bit
Safari 5.1.1
Update for Microsoft Windows
Update for Apple Mac OS X Lion
Apple Mac OS X Lion Uninstaller
iPad 2 WiFi + 3G (GSM)
iPad 2 WiFi + 3G (CDMA)
iPad (WiFi and WiFi + 3G)
iPhone 4 (GSM)
iPhone 4 (CDMA)
iPhone 3GS
iPod Touch (3rd Generation)
iPod Touch (4th Generation)
AppleTV
IPSW Links:
iMZDL: iOS 5 & Mac OS X 10.7
iTunes 10.5Beta7
Apple Mac OS X
Microsoft Windows
Microsoft Windows 64-bit
Safari 5.1.1
Update for Microsoft Windows
Update for Apple Mac OS X Lion
Apple Mac OS X Lion Uninstaller
WHATS New in IOS 5 beta7The following issues relate to using the 5.0 SDK to develop code.
Accounts
When creating an iCloud account, you can use any Apple ID as long as it is a full email address and not a MobileMe account. If you have a MobileMe account, you can move that account to iCloud. You can find more information on iCloud at: http://developer.apple.com/icloud
AirPlay
Starting in iOS 5, video content in applications and websites are AirPlay-enabled by default.
iOS 5 supports AirPlay of video via AV Foundation.
API Validation
NEW: Starting in iOS 5.0 development tools beta 7, it is possible to extract APIs used by an application and have them checked for private APIs usage. This option will be offered at Validation time.
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.
Slideshow settings are not remembered for slideshow playback (always plays back in Reflections theme). Screen savers settings are behaving properly.
Binary Compatibility
On applications linked against the iOS 5.0 SDK, scroll view content offsets will no longer be rounded to integral pixels during a pinch gesture.
Calendar
Birthday calendars are not currently available via the icloud.com website or in Windows. They will be available in a future release.
Core Image
Several filters have been added since beta 1. The current list now includes the following filters:
CIAdditionCompositing, CIAffineTransform, CICheckerboardGenerator, CIColorBlendMode, CIColorBurnBlendMode, CIColorControls, CIColorCube, CIColorDodgeBlendMode, CIColorInvert, CIColorMatrix, CIColorMonochrome, CIConstantColorGenerator, CICrop, CIDarkenBlendMode, CIDifferenceBlendMode, CIExclusionBlendMode, CIExposureAdjust, CIFalseColor, CIGammaAdjust, CIGaussianGradient, CIHardLightBlendMode, CIHighlightShadowAdjust, CIHueAdjust, CIHueBlendMode, CILightenBlendMode, CILinearGradient, CILuminosityBlendMode, CIMaximumCompositing, CIMinimumCompositing, CIMultiplyBlendMode, CIMultiplyCompositing, CIOverlayBlendMode, CIRadialGradient, CISaturationBlendMode, CIScreenBlendMode, CISepiaTone, CISoftLightBlendMode, CISourceAtopCompositing, CISourceInCompositing, CISourceOutCompositing, CISourceOverCompositing, CIStraightenFilter, CIStripesGenerator, CITemperatureAndTint, CIToneCurve, CIVibrance, CIVignette, and CIWhitePointAdjust
iBooks
iBooks 1.2.2 may fail to display some text or images in books. Please update to iBooks 1.3 in the App Store.
iCloud Backup
If you enable iCloud Backup, automatic backup with iTunes when syncing will be disabled. We also suggest that you manually back up your device with iTunes. Backups made with earlier versions of iOS 5 beta will soon become incompatible, and will no longer be available. It is strongly advised you upgrade to this version of the iOS 5 beta in order to continue backing up your devices.
iCloud Storage
NEW: Starting in iOS 5 beta 7, the requirements for specifying container identifier strings in your applications entitlements have changed. Each container identifier that does not include a wildcard character must exactly match the bundle identifier of an application published using the same team ID as your application. You are not required to include an entitlement that matches your app’s own bundle identifier; for example, a lite and pro version of your app could both specify the pro app’s bundle identifier to share the same container. The requirements for container identifiers that include wildcard characters have not changed, but you may need to update existing wildcard identifiers after changing any non-wildcard identifiers in your applications entitlements to match the new rules.
NEW: In this beta of iOS 5.0 the number of times an app can synchronize in quick succession with the servers has been reduced. If you are debugging your app and want to see whether your synchronize requests are being throttled, you can call the -[NSUbiquitousKeyValueStore _printDebugDescription] method directly in gdb. Please note that -[NSUbiquitousKeyValueStore _printDebugDescription] is an SPI so you are strongly advised not to use it in your app.
On KVS, the per-key limit has been raised to 64Kb (to match the per-app limit); and the maximum number of keys has been raised to 256.
During the iOS 5 beta period, any documents stored on the servers might be purged periodically before GM. Therefore, it is highly recommended that you do not store any critical documents or information on the servers.
Provisioning Profiles no longer need to be enabled for iCloud in the iOS Provisioning Portal. All newly generated provisioning profiles are now automatically enabled for iCloud. If you are using an Xcode managed Team Provisioning Profile, click refresh in the Xcode Organizer to obtain a new iCloud-enabled profile. To enable all other provisioning profiles for iCloud, simply regenerate your profiles in the iOS Provisioning Portal.
If your application is using the NSMetadataQuery class, you must set a predicate, the predicate is now honored. But the predicate is an NSPredicate-style predicate, not a Spotlight-style predicate an example of this is that you must use LIKE instead of = for wild card matching. The differences are defined in more detail at: Loading
In this beta, the setSortDescriptors: method of NSMetadataQuery is not supported.
To use iCloud prior to beta 5, you had to manually specify various container identifiers (your application’s Display set) within an Entitlements file for both of your Mac OS X and iOS projects.
Starting in beta 5, to enable iCloud storage within your apps, simply click the “Enable Entitlements” checkbox in the Summary pane of your project. Xcode will create a custom entitlements file for your project that automatically includes your Team ID. You can add additional iCloud Container values as required by your application. (Note that you must regenerate your existing provisioning profiles, either with Xcode or in the iOS Provisioning Portal, to use iCloud storage.)
If you specify a custom identifier string for your iCloud Key-Value Store or iCloud Container entitlement values, you no longer need to prepend your Team ID to the beginning of the string. Xcode will prepend your Team ID to these entries automatically
The container identifier string you pass to the URLForUbiquityContainerIdentifier: method of NSFileManager MUST include the team ID at the beginning of the string. As a convenience, if you pass nil, Foundation uses the first document container ID specified in your app’s entitlements.
There are issues using the Cloud Storage document API in conjunction with protected data which can lead to data corruption.
In this beta, file presenters (objects that adopt the NSFilePresenter protocol) do not receive some of the messages that theyre supposed to receive, especially:
presentedSubitemDidAppearAtURL:
presentedSubitemDidChangeAtURL:
You can workaround this by implementing the relinquishPresentedItemToWriter: method and checking to see if the writer actually wrote when your file presenter reacquires.
File presenters do receive presentedItemDidChange: messages in this beta.
While reporting a bug related to the iCloud storage interfaces, please include the logs collected during your debugging session. To generate these logs, you must install a special debug profile on your device.
The debug profile can be obtained from Sign in with your Apple ID - Apple Developer. This profile enables the generation of debug logs that are needed to diagnose any problems using iCloud storage. The instructions to collect the logs are:
Install the profile. (The easiest way to do this is to mail it to yourself and open the attachment on their device.)
Reproduce the bug.
Sync with iTunes to pull the logs off your device.
Attach the logs to your bug report. You can find the logs in ~/Library/Logs/CrashReporter/MobileDevice/DeviceName/DiagnosticLogs.
These logs can grow large very quickly, so you should remove the profile after you have reproduced the problem and pulled the logs for the bug report.
File names are case-insensitive in OS X but case-sensitive in iOS. This can lead to problems when syncing files between the two. You should take steps on iOS to avoid creating files whose names differ only by case.
Find My iPhone
After OTA update Find My iPhone does not work. To make it functional you can toggle the the Find My iPhone from OFF to ON in Settings.
GameKit
NEW: Auto-matching with the Turn-based view controller does not work. Invites or the direct auto-match API can be used as a workaround.
Match data for turn based matches is currently limited to 4 KB of data.
FIXED: Events will be passed to the delegate whenever a turn is made on a match, instead of just when it becomes the local players turn.
iMessage
iMessage beta 1 will be unable to communicate with iMessage users on beta 2 or later.
FIXED:Setup Assistant does not provide AppleID password as an input for the FaceTime in iMessage.
interface Builder
FIXED: When editing the value of a constraint in the inspector, the constraint remains selected, and the outline view continues to show the constraint as selected.
In XCode 4.2 when copying views (either a single view or multiple views), both the user defined constraints directly on the selected view and the user defined constraints between the views being copied are copied to the pasteboard.
Changing the segment style of an NSSegmentedControl object to "Automatic" might crash in documents using Cocoa Auto Layout. To workaround the issue use an explicit segment style such as Round or Textured, and at runtime, change the segment style to automatic using the setSegmentStyle: method.
iTunes
NEW: When trying to restore an iPhone 3GS or iPod touch 3rd generation device running Beta 6 to Beta 7 using iTunes, you will have to set the device into DFU or you can OTA update to Beta 7. To enter DFU mode you will have to:
Connect the device to USB on your Mac.
Turn the device off.
Launch iTunes on your Mac.
Hold down the Home and Power buttons for 10 seconds.
Continue holding the Home button but let go of the Power button.
Hold Home button for 13 seconds or until the device shows up in iTunes.
The version of iTunes that comes with beta 7 cannot sync devices that have the beta 6 software installed. To avoid this problem, do the following:
Sync any devices that have beta 6 installed to the version of iTunes that came with beta 6.
Upgrade iTunes to the version that comes with beta 7.
Connect the device and install the beta 7 software. (Understand that you might see a failure to sync error when you first connect the device.)
After installing the beta 7 software, restore from your the backup you made in step 1.
Mail
When changing the host name of an email account in settings, blank messages may be seen in the unified inbox. As a workaround, delete and re-add the account instead of changing its host name.
Music Player
When deleting a song or video from Music/Videos on the device it crashes the app.
OpenGLES
FIXED: After the lighting stage, whether lighting is enabled or not, the resulting color values are not clamped in GLKit/GLKEffects with either GLKLightingTypePerVertex or GLKLightingTypePerPixel set on the effect. As a result it is not uncommon to see differences in lighting between the two, especially when multiple lights are enabled. This differs from OpenGLES 1.1 which clamps color values after the lighting stage regardless of whether or not lighting is enabled.
OTA Software Update
Users who installed iOS 5 beta 6 over the air from iOS 5 beta 3 must first erase all content and settings by choosing Settings > General > Reset > Erase All Content and Settings in order to install iOS 5 beta 7 over the air. This only impacts users who did not update to iOS 5 beta 4.
If you are doing an OTA software update, you will need to re-sync your photos with iTunes."
FIXED: There may be some cases where purchases from the App Store or iTunes Store appear to be stalled because the device is downloading something else in the background. A workaround is to disconnect the device from power (unplug the device).
NEW: If you have a passcode set, it must be removed before updating to seed 7 from previous seeds. It can be re-enabled after the update is complete. Failure to do so may require iMessage to be re-enabled in settings.
Reminders
FIXED: If reminders syncing is enabled for a Yahoo account and there is no reminders collection on the server, it will continually get recreated by the phone. Due to a Yahoo server bug, that collection will show up as an event calendar.
Security
In iOS 5.0 signing of certificates with MD5 signatures is not supported. Please ensure that certificates use signature algorithms based on SHA1 or SHA2.
Simulator
Location services are not functional in iOS 4.3 simulator running on Mac OS 10.7 with Xcode 4.2.
Springboard
Push and local notifications for apps appear in the new Notification Center in iOS 5. Notification Center displays notifications that are considered "unread.” In order to accommodate push and local notifications that have no "unread" status, developers can use their application badge count to trigger a clearing of notifications from Notification Center. When an application clears its badge count (by setting it to zero), iOS 5 will clear its notifications from Notification Center.
UI Automation
There is a known issue when using the performTaskOnHost API in a UI Automation script. If the task being performed with the API outputs excessively (say, thousands of lines of text) to standard out or standard error, the task may deadlock until the timeout is reached, at which point it will throw a javascript exception.
The lock() and unlock() functions of UIATarget have been replaced with the lockForDuration(<seconds>) function.
Starting in iOS 5 beta 2, you can now trigger the execution of an UI Automation script on an iOS device from the host terminal by using the instruments tool. The command is:
instruments -w <device id> -t <template> <application>
When using the cli instruments for UI Automation you can now target the default Automation Template and pass the script and results path into the tool as environment variable options. For example:
instruments -w <device id> -t /Developer/Platforms/iPhoneOS.platform/Developer/Library/Instruments/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate <application> -e UIASCRIPT <script> -e UIARESULTSPATH <results path>
UIKit
In iOS 5.0 UIPickerView doesnt send its pickerView:didSelectRow:inComponent: delegate message due to a programatic selection.
Starting in iOS 5 beta 3, the exclusiveTouch property of UIControl has returned to its original default value of NO.
Returning nil from the tableView:viewForHeaderInSection: method (or its footer equivalent) is no longer sufficient to hide a header. You must override tableView:heightForHeaderInSection: and return 0.0 to hide a header.
In the iOS 5 beta, the UITableView class has two methods to move one cell from one row to another with defined parameters. These APIs are:
moveSection:toSection:
moveRowAtIndexPath:toIndexPath:
Using the UIWebView class in Interface Builder, setting transparent background color is possible in iOS 5. Developers compiling against the new SDK can check their XIB for the UIWebView transparent setting.
In the iOS 5 beta, the UINavigationBar, UIToolbar, and UITabBar implementations have changed so that the drawRect: method is not called on instances of these classes unless it is implemented in a subclass. Apps that have re-implemented drawRect: in a category on any of these classes will find that the drawRect: method isnt called. UIKit does link-checking to keep the method from being called in apps linked before iOS 5 but does not support this design on iOS 5 or later. Apps can either:
Use the customization API for bars that in iOS 5 and later, which is the preferred way.
Subclass UINavigationBar (or the other bar classes) and override drawRect: in the subclass.
The indexPathForRow:inSection:, section, and row methods of NSIndexPath now use NSInteger instead of NSUInteger, so that these types match with methods defined on UITableView.
We have changed the behavior of scrollToRowAtIndexPath:atScrollPosition:animated: such that UITableViewScrollPositionTop and UITableViewScrollPositionBottom now adjust for the top and bottom portions of the contentInset property.
NEW: In releases prior to iOS 5.0, the UIPopoverController class would unconditionally set the autoresizing masks of view controllers which were the content view controller of the popover controller. It would also unconditionally set the autoresizing masks of the views of view controllers pushed on to a UINavigationController object which was the content view controller of the popover controller.
In iOS 5.0, the UIPopoverController class will no longer do this for applications linked on iOS 5.0 or later. Developers should ensure that the autoresizing masks of views are set properly to allow for arbitrary resizing within any container, not just popovers. A mask of (UIViewAutoresizingFlexibleWidth | UIViewAutoresizingFlexibleHeight) would not be unreasonable.
The completion handler for saveToURL:forSaveOperation:completionHandler: is now being called outside of the coordinated write block, where it used to be called inside.
FIXED: The autosaveWithCompletionHandler: method will now only be called for period-based saves and it is safe to return without saving. Documents must save, though, if the saveToURL:forSaveOperation:completionHandler: method is invoked.
Safari and WebKit
In iOS 5, a new inherited CSS property, -webkit-overflow-scrolling, is available. The value touch allows the web developer to opt in to native-style scrolling in an overflow:scroll element. The default value for this property is auto, which allows single-finger scrolling without momentum.
The WebKit framework has picked up a newer WebKit engine, which closely matches Safari 5.1. Some areas to be aware of with the new WebKit framework on iOS:
There is a new HTML5-compliant parser.
Text layout width may change slightly because word-rounding behavior now has floating-point-based precision.
There is improved validation of the <input type=number> form field, which includes removing leading zeros and number formatting.
Touch events are now supported on input fields.
window.onerror is now supported.
There is a new user agent that does not have locale information in the User Agent string.
URLs are now canonicalized by making the scheme all lowercase. If a fake URL is used to pass information from a UIWebView back to native code, make sure that the scheme is always lowercase, or that the native code compares the scheme in a case-insensitive manner.
Wi-Fi Syncing
In iOS 5 beta 4 and later, wireless syncing is now available on Windows as well as the Mac. (This support requires OS X 10.6.8 or Lion.) You will see an option to enable wireless syncing when you connect your device to iTunes with the USB cable. It is recommended you perform your initial sync with a cable after restoring your device.
Wireless syncing is triggered automatically when the device is connected to power and on the same network as the paired computer. Or, you can manually trigger a sync from iTunes or from Settings > General > iTunes Sync (same network as paired computer required).
If you find issues with apps, media and/or photos synced to your device, you can reset then resync. From Settings > General > Reset, choose Erase all Content and Settings. Then reconnect to iTunes and sync again.
Xcode
NEW: Starting with Xcode 4.2 in iOS 5.0 beta 7, support to run and debug applications in the iOS 4.3 Simulator and on devices with iOS versions older than 4.2 is made optional and installed on demand. This support is no longer shipped as part of the core tools packaging, and made available for download and installation through the "Downloads" pane of the Xcode Preferences panel. A valid iOS developer ADC account is required to obtain this content.
To obtain the iOS 4.3 Simulator, select the "More Simulators…" item from the Run Destinations popup in the main toolbar. This will present the Downloads pane of the Preferences with UI to initiate the installation of the simulator.
To obtain iOS device support for pre-iOS 4.2 devices, connect a device and activate it for development in the Organizer. Xcode will provide a prompt to initiate the download of the device support components.
If the Xcode 4.2 in iOS 5.0 beta 7 is installed over a previous Xcode 4.2 beta or Xcode 4.1, the iOS 4.3 Simulator and device support from the previous install will already be present, and the additional components will display as "Installed" in the Downloads pane of the Xcode Preferences.
The installation packages for the downloaded components will be stored in ~Library/Developer/Xcode. When a new version of Xcode (beta or GM) will be installed, subsequent requests to install these components will use the local packages without requiring a new download.
In some cases, Xcode 4.2 Organizer does not display a device that is in restore mode. As a workaround you can use iTunes to restore.
In iOS 5 beta 5, iOS Simulator is not compatible with previous releases of the iCloud Developer Seed for OS X. It is highly recommended that you update to the latest iCloud Developer Seed to ensure compatibility.
iOS 5.0 SDK supports both iOS 4.3 and iOS 5.0 simulators.
Accounts
When creating an iCloud account, you can use any Apple ID as long as it is a full email address and not a MobileMe account. If you have a MobileMe account, you can move that account to iCloud. You can find more information on iCloud at: http://developer.apple.com/icloud
AirPlay
Starting in iOS 5, video content in applications and websites are AirPlay-enabled by default.
iOS 5 supports AirPlay of video via AV Foundation.
API Validation
NEW: Starting in iOS 5.0 development tools beta 7, it is possible to extract APIs used by an application and have them checked for private APIs usage. This option will be offered at Validation time.
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.
Slideshow settings are not remembered for slideshow playback (always plays back in Reflections theme). Screen savers settings are behaving properly.
Binary Compatibility
On applications linked against the iOS 5.0 SDK, scroll view content offsets will no longer be rounded to integral pixels during a pinch gesture.
Calendar
Birthday calendars are not currently available via the icloud.com website or in Windows. They will be available in a future release.
Core Image
Several filters have been added since beta 1. The current list now includes the following filters:
CIAdditionCompositing, CIAffineTransform, CICheckerboardGenerator, CIColorBlendMode, CIColorBurnBlendMode, CIColorControls, CIColorCube, CIColorDodgeBlendMode, CIColorInvert, CIColorMatrix, CIColorMonochrome, CIConstantColorGenerator, CICrop, CIDarkenBlendMode, CIDifferenceBlendMode, CIExclusionBlendMode, CIExposureAdjust, CIFalseColor, CIGammaAdjust, CIGaussianGradient, CIHardLightBlendMode, CIHighlightShadowAdjust, CIHueAdjust, CIHueBlendMode, CILightenBlendMode, CILinearGradient, CILuminosityBlendMode, CIMaximumCompositing, CIMinimumCompositing, CIMultiplyBlendMode, CIMultiplyCompositing, CIOverlayBlendMode, CIRadialGradient, CISaturationBlendMode, CIScreenBlendMode, CISepiaTone, CISoftLightBlendMode, CISourceAtopCompositing, CISourceInCompositing, CISourceOutCompositing, CISourceOverCompositing, CIStraightenFilter, CIStripesGenerator, CITemperatureAndTint, CIToneCurve, CIVibrance, CIVignette, and CIWhitePointAdjust
iBooks
iBooks 1.2.2 may fail to display some text or images in books. Please update to iBooks 1.3 in the App Store.
iCloud Backup
If you enable iCloud Backup, automatic backup with iTunes when syncing will be disabled. We also suggest that you manually back up your device with iTunes. Backups made with earlier versions of iOS 5 beta will soon become incompatible, and will no longer be available. It is strongly advised you upgrade to this version of the iOS 5 beta in order to continue backing up your devices.
iCloud Storage
NEW: Starting in iOS 5 beta 7, the requirements for specifying container identifier strings in your applications entitlements have changed. Each container identifier that does not include a wildcard character must exactly match the bundle identifier of an application published using the same team ID as your application. You are not required to include an entitlement that matches your app’s own bundle identifier; for example, a lite and pro version of your app could both specify the pro app’s bundle identifier to share the same container. The requirements for container identifiers that include wildcard characters have not changed, but you may need to update existing wildcard identifiers after changing any non-wildcard identifiers in your applications entitlements to match the new rules.
NEW: In this beta of iOS 5.0 the number of times an app can synchronize in quick succession with the servers has been reduced. If you are debugging your app and want to see whether your synchronize requests are being throttled, you can call the -[NSUbiquitousKeyValueStore _printDebugDescription] method directly in gdb. Please note that -[NSUbiquitousKeyValueStore _printDebugDescription] is an SPI so you are strongly advised not to use it in your app.
On KVS, the per-key limit has been raised to 64Kb (to match the per-app limit); and the maximum number of keys has been raised to 256.
During the iOS 5 beta period, any documents stored on the servers might be purged periodically before GM. Therefore, it is highly recommended that you do not store any critical documents or information on the servers.
Provisioning Profiles no longer need to be enabled for iCloud in the iOS Provisioning Portal. All newly generated provisioning profiles are now automatically enabled for iCloud. If you are using an Xcode managed Team Provisioning Profile, click refresh in the Xcode Organizer to obtain a new iCloud-enabled profile. To enable all other provisioning profiles for iCloud, simply regenerate your profiles in the iOS Provisioning Portal.
If your application is using the NSMetadataQuery class, you must set a predicate, the predicate is now honored. But the predicate is an NSPredicate-style predicate, not a Spotlight-style predicate an example of this is that you must use LIKE instead of = for wild card matching. The differences are defined in more detail at: Loading
In this beta, the setSortDescriptors: method of NSMetadataQuery is not supported.
To use iCloud prior to beta 5, you had to manually specify various container identifiers (your application’s Display set) within an Entitlements file for both of your Mac OS X and iOS projects.
Starting in beta 5, to enable iCloud storage within your apps, simply click the “Enable Entitlements” checkbox in the Summary pane of your project. Xcode will create a custom entitlements file for your project that automatically includes your Team ID. You can add additional iCloud Container values as required by your application. (Note that you must regenerate your existing provisioning profiles, either with Xcode or in the iOS Provisioning Portal, to use iCloud storage.)
If you specify a custom identifier string for your iCloud Key-Value Store or iCloud Container entitlement values, you no longer need to prepend your Team ID to the beginning of the string. Xcode will prepend your Team ID to these entries automatically
The container identifier string you pass to the URLForUbiquityContainerIdentifier: method of NSFileManager MUST include the team ID at the beginning of the string. As a convenience, if you pass nil, Foundation uses the first document container ID specified in your app’s entitlements.
There are issues using the Cloud Storage document API in conjunction with protected data which can lead to data corruption.
In this beta, file presenters (objects that adopt the NSFilePresenter protocol) do not receive some of the messages that theyre supposed to receive, especially:
presentedSubitemDidAppearAtURL:
presentedSubitemDidChangeAtURL:
You can workaround this by implementing the relinquishPresentedItemToWriter: method and checking to see if the writer actually wrote when your file presenter reacquires.
File presenters do receive presentedItemDidChange: messages in this beta.
While reporting a bug related to the iCloud storage interfaces, please include the logs collected during your debugging session. To generate these logs, you must install a special debug profile on your device.
The debug profile can be obtained from Sign in with your Apple ID - Apple Developer. This profile enables the generation of debug logs that are needed to diagnose any problems using iCloud storage. The instructions to collect the logs are:
Install the profile. (The easiest way to do this is to mail it to yourself and open the attachment on their device.)
Reproduce the bug.
Sync with iTunes to pull the logs off your device.
Attach the logs to your bug report. You can find the logs in ~/Library/Logs/CrashReporter/MobileDevice/DeviceName/DiagnosticLogs.
These logs can grow large very quickly, so you should remove the profile after you have reproduced the problem and pulled the logs for the bug report.
File names are case-insensitive in OS X but case-sensitive in iOS. This can lead to problems when syncing files between the two. You should take steps on iOS to avoid creating files whose names differ only by case.
Find My iPhone
After OTA update Find My iPhone does not work. To make it functional you can toggle the the Find My iPhone from OFF to ON in Settings.
GameKit
NEW: Auto-matching with the Turn-based view controller does not work. Invites or the direct auto-match API can be used as a workaround.
Match data for turn based matches is currently limited to 4 KB of data.
FIXED: Events will be passed to the delegate whenever a turn is made on a match, instead of just when it becomes the local players turn.
iMessage
iMessage beta 1 will be unable to communicate with iMessage users on beta 2 or later.
FIXED:Setup Assistant does not provide AppleID password as an input for the FaceTime in iMessage.
interface Builder
FIXED: When editing the value of a constraint in the inspector, the constraint remains selected, and the outline view continues to show the constraint as selected.
In XCode 4.2 when copying views (either a single view or multiple views), both the user defined constraints directly on the selected view and the user defined constraints between the views being copied are copied to the pasteboard.
Changing the segment style of an NSSegmentedControl object to "Automatic" might crash in documents using Cocoa Auto Layout. To workaround the issue use an explicit segment style such as Round or Textured, and at runtime, change the segment style to automatic using the setSegmentStyle: method.
iTunes
NEW: When trying to restore an iPhone 3GS or iPod touch 3rd generation device running Beta 6 to Beta 7 using iTunes, you will have to set the device into DFU or you can OTA update to Beta 7. To enter DFU mode you will have to:
Connect the device to USB on your Mac.
Turn the device off.
Launch iTunes on your Mac.
Hold down the Home and Power buttons for 10 seconds.
Continue holding the Home button but let go of the Power button.
Hold Home button for 13 seconds or until the device shows up in iTunes.
The version of iTunes that comes with beta 7 cannot sync devices that have the beta 6 software installed. To avoid this problem, do the following:
Sync any devices that have beta 6 installed to the version of iTunes that came with beta 6.
Upgrade iTunes to the version that comes with beta 7.
Connect the device and install the beta 7 software. (Understand that you might see a failure to sync error when you first connect the device.)
After installing the beta 7 software, restore from your the backup you made in step 1.
When changing the host name of an email account in settings, blank messages may be seen in the unified inbox. As a workaround, delete and re-add the account instead of changing its host name.
Music Player
When deleting a song or video from Music/Videos on the device it crashes the app.
OpenGLES
FIXED: After the lighting stage, whether lighting is enabled or not, the resulting color values are not clamped in GLKit/GLKEffects with either GLKLightingTypePerVertex or GLKLightingTypePerPixel set on the effect. As a result it is not uncommon to see differences in lighting between the two, especially when multiple lights are enabled. This differs from OpenGLES 1.1 which clamps color values after the lighting stage regardless of whether or not lighting is enabled.
OTA Software Update
Users who installed iOS 5 beta 6 over the air from iOS 5 beta 3 must first erase all content and settings by choosing Settings > General > Reset > Erase All Content and Settings in order to install iOS 5 beta 7 over the air. This only impacts users who did not update to iOS 5 beta 4.
If you are doing an OTA software update, you will need to re-sync your photos with iTunes."
FIXED: There may be some cases where purchases from the App Store or iTunes Store appear to be stalled because the device is downloading something else in the background. A workaround is to disconnect the device from power (unplug the device).
NEW: If you have a passcode set, it must be removed before updating to seed 7 from previous seeds. It can be re-enabled after the update is complete. Failure to do so may require iMessage to be re-enabled in settings.
Reminders
FIXED: If reminders syncing is enabled for a Yahoo account and there is no reminders collection on the server, it will continually get recreated by the phone. Due to a Yahoo server bug, that collection will show up as an event calendar.
Security
In iOS 5.0 signing of certificates with MD5 signatures is not supported. Please ensure that certificates use signature algorithms based on SHA1 or SHA2.
Simulator
Location services are not functional in iOS 4.3 simulator running on Mac OS 10.7 with Xcode 4.2.
Springboard
Push and local notifications for apps appear in the new Notification Center in iOS 5. Notification Center displays notifications that are considered "unread.” In order to accommodate push and local notifications that have no "unread" status, developers can use their application badge count to trigger a clearing of notifications from Notification Center. When an application clears its badge count (by setting it to zero), iOS 5 will clear its notifications from Notification Center.
UI Automation
There is a known issue when using the performTaskOnHost API in a UI Automation script. If the task being performed with the API outputs excessively (say, thousands of lines of text) to standard out or standard error, the task may deadlock until the timeout is reached, at which point it will throw a javascript exception.
The lock() and unlock() functions of UIATarget have been replaced with the lockForDuration(<seconds>) function.
Starting in iOS 5 beta 2, you can now trigger the execution of an UI Automation script on an iOS device from the host terminal by using the instruments tool. The command is:
instruments -w <device id> -t <template> <application>
When using the cli instruments for UI Automation you can now target the default Automation Template and pass the script and results path into the tool as environment variable options. For example:
instruments -w <device id> -t /Developer/Platforms/iPhoneOS.platform/Developer/Library/Instruments/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate <application> -e UIASCRIPT <script> -e UIARESULTSPATH <results path>
UIKit
In iOS 5.0 UIPickerView doesnt send its pickerView:didSelectRow:inComponent: delegate message due to a programatic selection.
Starting in iOS 5 beta 3, the exclusiveTouch property of UIControl has returned to its original default value of NO.
Returning nil from the tableView:viewForHeaderInSection: method (or its footer equivalent) is no longer sufficient to hide a header. You must override tableView:heightForHeaderInSection: and return 0.0 to hide a header.
In the iOS 5 beta, the UITableView class has two methods to move one cell from one row to another with defined parameters. These APIs are:
moveSection:toSection:
moveRowAtIndexPath:toIndexPath:
Using the UIWebView class in Interface Builder, setting transparent background color is possible in iOS 5. Developers compiling against the new SDK can check their XIB for the UIWebView transparent setting.
In the iOS 5 beta, the UINavigationBar, UIToolbar, and UITabBar implementations have changed so that the drawRect: method is not called on instances of these classes unless it is implemented in a subclass. Apps that have re-implemented drawRect: in a category on any of these classes will find that the drawRect: method isnt called. UIKit does link-checking to keep the method from being called in apps linked before iOS 5 but does not support this design on iOS 5 or later. Apps can either:
Use the customization API for bars that in iOS 5 and later, which is the preferred way.
Subclass UINavigationBar (or the other bar classes) and override drawRect: in the subclass.
The indexPathForRow:inSection:, section, and row methods of NSIndexPath now use NSInteger instead of NSUInteger, so that these types match with methods defined on UITableView.
We have changed the behavior of scrollToRowAtIndexPath:atScrollPosition:animated: such that UITableViewScrollPositionTop and UITableViewScrollPositionBottom now adjust for the top and bottom portions of the contentInset property.
NEW: In releases prior to iOS 5.0, the UIPopoverController class would unconditionally set the autoresizing masks of view controllers which were the content view controller of the popover controller. It would also unconditionally set the autoresizing masks of the views of view controllers pushed on to a UINavigationController object which was the content view controller of the popover controller.
In iOS 5.0, the UIPopoverController class will no longer do this for applications linked on iOS 5.0 or later. Developers should ensure that the autoresizing masks of views are set properly to allow for arbitrary resizing within any container, not just popovers. A mask of (UIViewAutoresizingFlexibleWidth | UIViewAutoresizingFlexibleHeight) would not be unreasonable.
The completion handler for saveToURL:forSaveOperation:completionHandler: is now being called outside of the coordinated write block, where it used to be called inside.
FIXED: The autosaveWithCompletionHandler: method will now only be called for period-based saves and it is safe to return without saving. Documents must save, though, if the saveToURL:forSaveOperation:completionHandler: method is invoked.
Safari and WebKit
In iOS 5, a new inherited CSS property, -webkit-overflow-scrolling, is available. The value touch allows the web developer to opt in to native-style scrolling in an overflow:scroll element. The default value for this property is auto, which allows single-finger scrolling without momentum.
The WebKit framework has picked up a newer WebKit engine, which closely matches Safari 5.1. Some areas to be aware of with the new WebKit framework on iOS:
There is a new HTML5-compliant parser.
Text layout width may change slightly because word-rounding behavior now has floating-point-based precision.
There is improved validation of the <input type=number> form field, which includes removing leading zeros and number formatting.
Touch events are now supported on input fields.
window.onerror is now supported.
There is a new user agent that does not have locale information in the User Agent string.
URLs are now canonicalized by making the scheme all lowercase. If a fake URL is used to pass information from a UIWebView back to native code, make sure that the scheme is always lowercase, or that the native code compares the scheme in a case-insensitive manner.
Wi-Fi Syncing
In iOS 5 beta 4 and later, wireless syncing is now available on Windows as well as the Mac. (This support requires OS X 10.6.8 or Lion.) You will see an option to enable wireless syncing when you connect your device to iTunes with the USB cable. It is recommended you perform your initial sync with a cable after restoring your device.
Wireless syncing is triggered automatically when the device is connected to power and on the same network as the paired computer. Or, you can manually trigger a sync from iTunes or from Settings > General > iTunes Sync (same network as paired computer required).
If you find issues with apps, media and/or photos synced to your device, you can reset then resync. From Settings > General > Reset, choose Erase all Content and Settings. Then reconnect to iTunes and sync again.
Xcode
NEW: Starting with Xcode 4.2 in iOS 5.0 beta 7, support to run and debug applications in the iOS 4.3 Simulator and on devices with iOS versions older than 4.2 is made optional and installed on demand. This support is no longer shipped as part of the core tools packaging, and made available for download and installation through the "Downloads" pane of the Xcode Preferences panel. A valid iOS developer ADC account is required to obtain this content.
To obtain the iOS 4.3 Simulator, select the "More Simulators…" item from the Run Destinations popup in the main toolbar. This will present the Downloads pane of the Preferences with UI to initiate the installation of the simulator.
To obtain iOS device support for pre-iOS 4.2 devices, connect a device and activate it for development in the Organizer. Xcode will provide a prompt to initiate the download of the device support components.
If the Xcode 4.2 in iOS 5.0 beta 7 is installed over a previous Xcode 4.2 beta or Xcode 4.1, the iOS 4.3 Simulator and device support from the previous install will already be present, and the additional components will display as "Installed" in the Downloads pane of the Xcode Preferences.
The installation packages for the downloaded components will be stored in ~Library/Developer/Xcode. When a new version of Xcode (beta or GM) will be installed, subsequent requests to install these components will use the local packages without requiring a new download.
In some cases, Xcode 4.2 Organizer does not display a device that is in restore mode. As a workaround you can use iTunes to restore.
In iOS 5 beta 5, iOS Simulator is not compatible with previous releases of the iCloud Developer Seed for OS X. It is highly recommended that you update to the latest iCloud Developer Seed to ensure compatibility.
iOS 5.0 SDK supports both iOS 4.3 and iOS 5.0 simulators.
Wednesday, September 11, 2013
How to Jailbreak iOS 4 3 3 iPhone 4 3GS iPod Touch 4G 3G iPad Redsn0w 0 9 6rc16
If you are interested in video guides, heres a good one to untethered jailbreak your iPhone 4, 3GS, iPod touch 4G, 3G or iPad using Redsn0w 0.9.6rc16.
If your iPhone 4, 3GS relies on ultrasn0w unlock you should stay away from redsn0w, you have to restore your iPhone via pre-jailbroken custom firmware, simply you have to Click Here (sn0wbreeze 2.7.1 for Windows) or Click Here (PwnageTool 4.3.3.1 for Mac) to preserve your old baseband to unlock it with ultrasn0w.
Download Redsn0w 0.9.6rc16 for Windows
Download Redsn0w 0.9.6rc16 for Mac
Download iOS 4.3.3 for iPhone, iPod touch, iPad
Download iTunes 10.2.2
Read more...
If your iPhone 4, 3GS relies on ultrasn0w unlock you should stay away from redsn0w, you have to restore your iPhone via pre-jailbroken custom firmware, simply you have to Click Here (sn0wbreeze 2.7.1 for Windows) or Click Here (PwnageTool 4.3.3.1 for Mac) to preserve your old baseband to unlock it with ultrasn0w.
Download Redsn0w 0.9.6rc16 for Windows
Download Redsn0w 0.9.6rc16 for Mac
Download iOS 4.3.3 for iPhone, iPod touch, iPad
Download iTunes 10.2.2
Jailbreak 5 0 1 Untethered iPhone 4 3GS iPod Touch 4G 3G iPad with Redsn0w 0 9 10 b1
Jailbreak 5.0.1 untethered now became a reality. The iPhone Dev-team has just pushed Redsn0w 0.9.10 b1 to jailbreak 5.0.1 untethered on iPhone 4, 3GS, iPod touch 4G, 3G and iPad 1. Pod2g was the guy behind 5.0.1 untethered jailbreak, as he handed over his project to both Chronic Dev-team and iPhone Dev-team. The two teams have made a major task on 5.0.1 untethered jailbreak. iPhone Dev-team have put 5.0.1 untethered in to RedsnOw 0.9.10 b1 and PwnageTool. Chronic Dev-team put untethered 5.0.1 jailbreak into a Cydia package, thanks Pod2g and the both teams for making us happy.
Supported devices :
Required Downloads :
Step 1: Connect your iDevice with your PC via USB, and open iTunes then Restore to iOS 5.0.1 (If you are already running iOS 5.0.1, bypass this step)
Step 2: Start Redsn0w 0.9.10 b1, and press on "Jailbreak" button
Step 3: Now select “Install Cydia” and click “Next”.
Step 4: Now make sure your device is both OFF and PLUGGED IN to the computer before you click “Next”.
At this stage you will be presented with a screen where you will be guided on how to enter DFU mode. Quickly hold “Power” button and then while holding the “Power” button, you will now have to hold “Home” button too. Now after few seconds release “Power” button but keep holding “Home” button until installation begins.
Before starting to jailbreak 5.0.1untethered on iPhone 4, 3GS, iPod touch 4G, 3G and iPad - You have to know this :
Supported devices :
- iPhone 4 (GSM - CDMA)
- iPhone 3GS
- iPod touch 4G
- iPod touch 3G
- iPad 1
- If you have one of those devices and are not on 5.0.1 yet, update now! The SHSH window is still open for 5.0.1 If you unlock via ultrasn0w or gevey, make sure you only get to 5.0.1 via a custom IPSW! Once you’re at 5.0.1, use the latest redsn0w 0.9.10 to both jailbreak and untether.
- If you’re already at 5.0.1 with a tethered jailbreak, you have two choices: either run redsn0w 0.9.10 over your current jailbreak (deselect “Install Cydia” if you do that), or install the Cydia package prepared by the chronic devteam. The patches are the same regardless of which you choose.
- Some of you are using a hybrid 5.0/5.0.1 configuration. If so, do not attempt to install this untether over that setup! You will most likely get into a reboot cycle. Do a sync and fresh restore to 5.0.1 then install the jailbreak + untether.
How to jailbreak 5.0.1 untethered iPhone 4, 3GS, iPod touch 4G, 3G, iPad 1 - [Tutorial]
Required Downloads :
- Download Redsn0w 0.9.10 - Windows (be sure to run in Administrator mode)
- Download Redsn0w 0.9.10 - Mac
- Download iOS 5.0.1 ipsw for iPhone, iPod touch or iPad
- Download iTunes
Step 1: Connect your iDevice with your PC via USB, and open iTunes then Restore to iOS 5.0.1 (If you are already running iOS 5.0.1, bypass this step)
Step 2: Start Redsn0w 0.9.10 b1, and press on "Jailbreak" button
Step 3: Now select “Install Cydia” and click “Next”.
At this stage you will be presented with a screen where you will be guided on how to enter DFU mode. Quickly hold “Power” button and then while holding the “Power” button, you will now have to hold “Home” button too. Now after few seconds release “Power” button but keep holding “Home” button until installation begins.
Subscribe to:
Posts (Atom)