iOS 11.1 Beta 3 Bug Fixes, Changes and Improvements

Status
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.

SumYoungGai

macrumors 6502a
Original poster
Jun 11, 2013
689
617
SF Bay Area, CA
iOS 11.1 beta 3

Release Date — October 16, 2017
Build Number — 15B5086a
Darwin Kernel Version — 17.2.0 Sat Sep 30 23:14:13 PDT 2017

New Features & Changes

  • Haptic Feedback occurs on incorrect passcode entry.
  • Blurred Springboard is shown in empty reachability space (see this post)
  • Messages now has a new splash screen for Apple Pay Cash setup on first opening the app
Remaining Issues
  • Calculator still buggy.
  • Accessing WiFi through 3D Touch on Settings app does not show list of networks.
  • Control Centre swipe up animation stutters within various third-party apps.
  • iBooks third-party app text-highlights sharing missing.
  • Trashing Office 365 emails from a notification still does nothing and leaves email in inbox
  • Scheduled fetch and notifications feature not coming for favorited folders and sub folders in stock mail app.
New Issues
  • No security code or touch id is asked when unlocking the phone previously blocked during a call with audio forwarded to airpods
  • iPad 10.5 Safari: Distinct 1-2 sec delay when tapping address bar field.
Resolved Issues
  • "KRACK" WiFi vulnerability has been fixed.
  • 3D Touch no longer stutters.
  • Accessing cover sheet while using reachability works as it did in iOS 10.
  • Resolved an issue where Apple Pay Cash may request you accept the Terms and Conditions a second time in the messages app when attempting to send someone money
  • Qualcomm iPhone 7 Plus: 3.21.01
  • Qualcomm iPhone 7: 3.21.01
  • Intel iPhone 7 Plus: 2.01.03
  • Qualcomm iPhone 8 Plus: 1.41.00

United States

  • Verizon - 30.0
  • Verizon iPads -
  • T-Mobile - 30.0
  • AT&T - 30.0
  • MetroPCS -
  • U.S. Cellular - 30.0
  • Sprint -30.0
United Kingdom
  • O2-UK -
  • BT-UK -
  • Three -
  • EE - 30.0
  • Vodafone UK -
Canada
  • Videotron -
  • Rogers -
  • Fido -
  • Bell -
  • Telus -
France
  • Orange France -
Germany
  • O2-DE -
  • Vodafone.de - 30.0
  • Telekom.de 30.0
Netherlands
  • KPN -
Southeast Asia
  • Singapore Singtel -
  • Philippines Globe -
  • Thailand AIS -
Sweden
  • Comviq - 30.0
  • Tre -
Ireland
  • Meteor
Australia
  • Optus -
  • Telstra -
Turkey
  • Turkcell - 30.0
  • Vodafone TR - 29.5
Poland
  • T-Mobile -
  • Orange -
India
  • Airtel - 30
  • Jio - 30
Other
  • TIGO GT - 30.0
  • Docomo - 30.0
  • AlwaysOnline -
 
Last edited by CMoore515:

WaruiKoohii

macrumors 6502
Oct 4, 2015
350
347
Boston
Highly, highly unlikely. This build is 2-3 weeks old internally. iPhone X units have already shipped with the final 11.1 installed. We won't see a fix for that until 11.1.1 (or 11.0.4 for those not running betas).
It's possible, and no the build is not 2-3 weeks old internally.

It's possible because the vulnerability has been known within the industry for weeks at this point, which is how Microsoft has already pushed out a fix over Windows Update, how Intel already has updated firmware for many of their WiFi modules, and how the WiFi standards group has been able to publish fixes for router and AP makers to implement (and how a handful already have implemented in firmware updates).
 

uandme72

macrumors 6502a
Mar 2, 2015
724
90
Highly, highly unlikely. This build is 2-3 weeks old internally. iPhone X units have already shipped with the final 11.1 installed. We won't see a fix until 11.1.1 for that (or 11.0.4 for those not running betas).
But the users here are not talking about X.
Irrespective of the release of 11 for X, the development cycle would not stop and the fixes we see in this beta may be released in the next update.
But then apple would have to release some build for 11.1 publicly.
 

Mlrollin91

macrumors G5
Nov 20, 2008
13,475
8,685
Ventura County
It's possible, and no the build is not 2-3 weeks old internally.

It's possible because the vulnerability has been known within the industry for weeks at this point, which is how Microsoft has already pushed out a fix over Windows Update.
Yes, the build is 2-3 weeks old internally. Internally they are running beta 5. Check out the iOS 11 speculation thread for more detail.
 
  • Like
Reactions: Netman and g-7

Mlrollin91

macrumors G5
Nov 20, 2008
13,475
8,685
Ventura County
But the users here are not talking about X.
Irrespective of the release of 11 for X, the development cycle would not stop and the fixes we see in this beta may be released in the next update.
But then apple would have to release some build for 11.1 publicly.
Check the Darwin Kernal Version for this build, it will be at least 7-10 days ago. This is an old build. Therefore this would not contain a fix for something that was made public today. iOS 11.1 is completely centered around iPhone X.
 

WaruiKoohii

macrumors 6502
Oct 4, 2015
350
347
Boston
Yes, the build is 2-3 weeks old internally. Internally they are running beta 5. Check out the iOS 11 speculation thread for more detail.
It doesn't make sense for Apple to sit on a build for weeks. They want people testing it ASAP. You can see this in action if you compare the kernel build time stamps on builds with updated kernels against the builds release date. Usually within a week to a few days.
 
Last edited by Weaselboy:

uandme72

macrumors 6502a
Mar 2, 2015
724
90
Check the Darwin Kernal Version for this build, it will be at least 7-10 days ago. This is an old build. Therefore this would not contain a fix for something that was made public today. iOS 11.1 is completely centered around iPhone X.
agreed.
but does apple still have to release 11.1 publicly or this beta cycle will not culminate in a public release.
 

Mlrollin91

macrumors G5
Nov 20, 2008
13,475
8,685
Ventura County
I trust the iOS speculation thread as much as I trust Trump when he says he stands for gay rights. It's just a bunch of fans saying what they think will happen.

It doesn't make sense for Apple to sit on a build for weeks. They want people testing it ASAP. You can see this in action if you compare the kernel build time stamps on builds with updated kernels against the builds release date. Usually within a week to a few days.
See, if you would read the thread you would learn that there are people that actually know its on beta 5 because they have access to devices running beta 5 for Apple Pay purposes with banks.
 

WaruiKoohii

macrumors 6502
Oct 4, 2015
350
347
Boston
Check the Darwin Kernal Version for this build, it will be at least 7-10 days ago. This is an old build. Therefore this would not contain a fix for something that was made public today. iOS 11.1 is completely centered around iPhone X.
The vulnerability was made public today, but Apple has known about it for weeks. That's how some companies (such as Microsoft) were able to patch the vulnerability before the public announcement.
[doublepost=1508174602][/doublepost]
See, if you would read the thread you would learn that there are people that actually know its on beta 5 because they have access to devices running beta 5 for Apple Pay purposes with banks.
Speculation threads for anything are a waste of time to read, honestly. There are better places to get speculative news than a bunch of people on a website.

On the chance that some people are already on Beta 5, you -need- to consider that Beta # in one ring does -not- correlate to Beta # on another ring. For reference, see the Beta # disparity between Developer and Public.
 
  • Like
Reactions: mr100percent

Mlrollin91

macrumors G5
Nov 20, 2008
13,475
8,685
Ventura County
The vulnerability was made public today, but Apple has known about it for weeks. That's how some companies (such as Microsoft) were able to patch the vulnerability before the public announcement.
[doublepost=1508174602][/doublepost]
Speculation threads for anything are a waste of time to read, honestly. There are better places to get speculative news than a bunch of people on a website.
And yet you completely missed what I said and went on your rant about speculation threads.
 

WaruiKoohii

macrumors 6502
Oct 4, 2015
350
347
Boston
And yet you completely missed what I said and went on your rant about speculation threads.
I made an edit you should see.

On the chance that some people are already on Beta 5, you -need- to consider that Beta # in one ring does -not- correlate to Beta # on another ring. For reference, see the Beta # disparity between Developer and Public.
 

Mlrollin91

macrumors G5
Nov 20, 2008
13,475
8,685
Ventura County
I made an edit you should see.

On the chance that some people are already on Beta 5, you -need- to consider that Beta # in one ring does -not- correlate to Beta # on another ring. For reference, see the Beta # disparity between Developer and Public.
Different beta "number" but still same build number. PB and DP are always different beta numbers, but always same build number.
 

crawfish963

macrumors 6502a
Apr 16, 2010
548
289
Texas
The vulnerability was made public today, but Apple has known about it for weeks. That's how some companies (such as Microsoft) were able to patch the vulnerability before the public announcement.
[doublepost=1508174602][/doublepost]
Speculation threads for anything are a waste of time to read, honestly. There are better places to get speculative news than a bunch of people on a website.

On the chance that some people are already on Beta 5, you -need- to consider that Beta # in one ring does -not- correlate to Beta # on another ring. For reference, see the Beta # disparity between Developer and Public.
It’s always fun coming in and seeing how people like you derail these threads. Take this argument to a PM. The rest of us came for actual information regarding fixes and problems from the software update.
 

Broken Hope

macrumors 6502a
Jan 15, 2015
986
702
See, if you would read the thread you would learn that there are people that actually know its on beta 5 because they have access to devices running beta 5 for Apple Pay purposes with banks.
Without knowing what build number the beta 5 is we have no idea how much older/newer this build is.
 

Status
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.