All Devices iOS 13.1 Beta 2 ― Bug Fixes, Changes, and Improvements

[eicca]

Neither my iPad or iPhone are having battery drain problem. The iPhone seems to last a little less than on 12.4, but nothing significant.

Mail even seems to be working fine for me too, using a Gmail account. The weirdest thing it does is give me the notification before the message has actually downloaded, but it’s still been totally useable for me.

 

[itsmilo]

Just had a weird issue where WiFi would automatically enable itself right after disabling it from control center and then the settings app would open to a black screen and not load. Had to force restart the phone to fix it. Not sure what caused it

 

[Ateebn]

Hi, I started the update over 2 hours ago on my iphone xs max, but it is stuck on the apple logo and the progress bar is full. Every time i try to hard reset it, I get the message that the phone will reboot when update is complete, but been saying that for 2 hours.

can someone help?

 

[cbreze]

This last update fixed my gmail account forwarding issues, sweet

 

[d123]

I’ve never had the level of drain in ANY beta, like I had in iOS 13.1 b2. 75% in 3 hours

My iPhone XR on 13.1 b2 is now on 75% (came off charge at 00:02 and it’s now 23:07), so it’s been 23 hours since it came off charge.

So 25% “drain” in 23 hours...

 

[dk001]

iOS 13.1 is extremely polished in its current state unless the sole function of your iPhone is email with the stock Mail app. Even then you could get by with a few minor annoyances.

12.4.1 is out of date. I lingered up until a few days ago and now that I’ve updated I realize my hang ups on 3D Touch and stability in general were misplaced. Haptic Touch is just as, if not more effective and intuitive and the dark mode option is a bonus.

Extremely polished? We have differing definitions obviously.

 

[gwhizkids]

Extremely polished? We have differing definitions obviously.

More like differing experiences. For me, it has also been extremely stable and fairly polished. But that doesn’t mean it has been that way for you. The question is: how has it been for the majority of beta users?

 

[AZhappyjack]

More like differing experiences. For me, it has also been extremely stable and fairly polished. But that doesn’t mean it has been that way for you. The question is: how has it been for the majority of beta users?

I'm actually pretty happy with iOS 13.1 b2... in my case, it seems quite good... no issues to report...

 

[TallRed]

More like differing experiences. For me, it has also been extremely stable and fairly polished. But that doesn’t mean it has been that way for you. The question is: how has it been for the majority of beta users?

Mostly ok. I’ve noticed that more robocallers are getting through the “Do Not Disturb” feature. Sometimes there are cosmetic glitches that weren’t there before. An example would be certain popup boxes which when tapped give a strange highlight to the text in the box. It’s annoying but not a deal breaker. The failure of the Do Not Disturb feature is troubling, though.

 

[MozMan68]

Mostly ok. I’ve noticed that more robocallers are getting through the “Do Not Disturb” feature. Sometimes there are cosmetic glitches that weren’t there before. An example would be certain popup boxes which when tapped give a strange highlight to the text in the box. It’s annoying but not a deal breaker. The failure of the Do Not Disturb feature is troubling, though.

How is that even possible?

If they are not in your contacts, it doesn’t answer.

Edit: and sorry...I just reread and saw you are talking about Do Not Disturb, not “Silence Unknown Callers”.

Are you sure your phone is “off” during the DND time period? If you are using it, that overrides DND and you will still get calls/notifications.

 

[gwhizkids]

What I’d like to know is (A) are developers developing their soon to be released apps against 13. 0 b8 or 13.1? and (b) are developers running into more or fewer issues with 13.1 vs 13.0 b8?

 

[Sharkoneau]

Been bothering me for a while, so I decided to submit one of my more important suggestions to date:

That said, I’d really appreciate everyone’s support on this!

 

[AZhappyjack]

What I’d like to know is (A) are developers developing their soon to be released apps against 13. 0 b8 or 13.1? and (b) are developers running into more or fewer issues with 13.1 vs 13.0 b8?

I don't see a different set of development tools for iOS 13.0 and iOS 13.1... maybe I missed something... but I'm not convinced that there is a functional difference.

 

[Eksoccer99]

Oh really?? I swear it would still mark them as read when swiping to clear in iOS 12. What you say makes sense, but it only recently started not marking messages as read on the 13 betas for me.

Thanks!

My wife’s phone is on 12.4.1. Swipe to clear still left the message unread with a badge count when unlocked.

 

[hNicolas]

I haven’t had any problems with my 10R, everything is running well and smoothly. No battery drain, in fact I’m getting excellent battery use since 13.1 beta 2.

I use apple mail with 2 iCloud accounts, Gmail, Yahoo and 2 private business accounts. All are running perfectly now with badges working as they should. Even one of my banking apps (RBC mobile) that always crashed when logging in since beta 6 was fixed with the last update.

For me (personally) this latest 13.1 b2 whether it’s GM or not, is probably the most stable iOS beta I have ever used leading up to release, and I’m going way back to the beginning of iPhone time

 

[dreadlord]

What I’d like to know is (A) are developers developing their soon to be released apps against 13. 0 b8 or 13.1? and (b) are developers running into more or fewer issues with 13.1 vs 13.0 b8?

There are no SDK changes in iOS 13.1 betas (that's why they have letter "A" in the build number instead of "B"). Therefore, they are developing their apps against the latest SDK which is iOS 13.1.

This is why I do think iOS 13.1 will be the final release. Because of the tariffs, Apple packaged many 2019 iPhones with an early release iOS 13 (probably beta 8?). This means that the development of the software installed on 2019 iPhones was ended 1-2 week earlier than previous major releases, iOS 11, for example. There must be a Day 1 patch to these devices when they are released. The launch date will also be the date iOS 13 released to older devices. At this point, I would assume iOS 13.0.1 would be the final release. However, iOS 13.1 is just a bug fix update with enabled features that are disabled in iOS 13.0.

On September 16/17, Apple will release iOS 13. The update will be labeled as "iOS 13" on older devices but it will be shown as iOS 13.1 in About after installing the update (just like iOS 10.0.1 release which was labeled as jus "iOS 10" on older devices but labeled as "iOS 10.0.1" on iPhone 7 devices). The 2019 iPhones will get the same version but correctly labeled as "iOS 13.1" for those devices.

By saying "labeled", I mean the update name shown in Settings->General->Software Update when a new update released. You can see that by checking update on a device that supports iOS 12 but currently running iOS 11. When you check updates on that device, it will just say "iOS 12". But if you install this update it will install iOS 12.4.1 the latest version.

 

[gwhizkids]

There are no SDK changes in iOS 13.1 betas (that's why they have letter "A" in the build number instead of "B"). Therefore, they are developing their apps against the latest SDK which is iOS 13.1.

This is why I do think iOS 13.1 will be the final release. Because of the tariffs, Apple packaged many 2019 iPhones with an early release iOS 13 (probably beta 8?). This means that the development of the software installed on 2019 iPhones was ended 1-2 week earlier than previous major releases, iOS 11, for example. There must be a Day 1 patch to these devices when they are released. The launch date will also be the date iOS 13 released to older devices. At this point, I would assume iOS 13.0.1 would be the final release. However, iOS 13.1 is just a bug fix update with enabled features that are disabled in iOS 13.0.

On September 16/17, Apple will release iOS 13. The update will be labeled as "iOS 13" on older devices but it will be shown as iOS 13.1 in About after installing the update (just like iOS 10.0.1 release which was labeled as jus "iOS 10" on older devices but labeled as "iOS 10.0.1" on iPhone 7 devices). The 2019 iPhones will get the same version but correctly labeled as "iOS 13.1" for those devices.

By saying "labeled", I mean the update name shown in Settings->General->Software Update when a new update released. You can see that by checking update on a device that supports iOS 12 but currently running iOS 11. When you check updates on that device, it will just say "iOS 12". But if you install this update it will install iOS 12.4.1 the latest version.

I tend to agree with you.

 

[Knowlege Bomb]

Extremely polished? We have differing definitions obviously.

Imagine that!

What issues are you experiencing that disqualify the "polished" moniker for you?

 

[dk001]

Imagine that!

What issues are you experiencing that disqualify the "polished" moniker for you?

Have you been reading this thread?
While I could compile a list of the issues I have found, a bigger flag is the dramatic number of issues found that affect some one way, others a different way, and others not at all.
For you it may be " polished " and do what you need. For others, including myself, this is not a " polished " version and not something I can rely on for critical devices.
Behavior of a release like this indicates there are changes that have happened and still going on that are effecting other functions. When an OTA, a manual wipe and restore, a restore as new, or start over from scratch all uncover, fix, or rediscover issues, different issues, it needs a bit more work IMO before we can say " polished ".

 

[Knowlege Bomb]

Have you been reading this thread?

Yes.

While I could compile a list of the issues I have found, a bigger flag is the dramatic number of issues found that affect some one way, others a different way, and others not at all.

Not sure what this has to do with my experiences.

For you it may be " polished " and do what you need.

I guess I should preface all future posts with a disclaimer that I'm not speaking for anybody but myself and my own experiences.

For others, including myself, this is not a " polished " version and not something I can rely on for critical devices.
Behavior of a release like this indicates there are changes that have happened and still going on that are effecting other functions. When an OTA, a manual wipe and restore, a restore as new, or start over from scratch all uncover, fix, or rediscover issues, different issues, it needs a bit more work IMO before we can say " polished ".

Yep. Different experiences for different devices with different setups and usage cases. I was simply asking you what your specific issues were and if your initial condescending question was meant to infer I should remember what you've posted in the previous 18 pages of messages then I apologize for my lack of a photographic memory.

 

[anticipate]

iOS 13.1 B2 seems good enoug for a wide release to me. (A huge step up from 13.1 B1). It still has some bugs and could use another pass, but it's fairly solid for an Apple release.

It always takes them a few versions to get it right (13.2, 13.3...)

 

[dk001]

Yes.



Not sure what this has to do with my experiences.




I guess I should preface all future posts with a disclaimer that I'm not speaking for anybody but myself and my own experiences.



Yep. Different experiences for different devices with different setups and usage cases. I was simply asking you what your specific issues were and if your initial condescending question was meant to infer I should remember what you've posted in the previous 18 pages of messages then I apologize for my lack of a photographic memory.

Like I initially said; your definition and mine differ. Not condescending in any fashion. I am surprised reading these last couple of threads you do not see why some of us have issues and are concerned. The wide ranging differences in basic core app functionality for the same devices or even across devices is a giant red flag for me.
I am running this on an IPP and an XS Max. Linked into this is my AW4, rMB 2015, iPad mini 4, iPhone 7, 7+, and X. All but my two are on the latest released version. Just for clarity my main device is a Razer.

If you would like a breakdown of my issues I will put it together and publish later.

 

[prk60091]

There are a lot of people with major batter draining issues going on with 13.1 beta 2. I’ve never had this before in any beta, ever. If not installed any new apps in the last few months of changed my habits, get in 3 hours or so, I lost 75% with no apps open, screen off and locked. There are others with similar experiences. iOS 13 b8 was better for me.

I’d expect this to be resolved, but if I was aware of this going in, I’d have skipped it.

in the past battery drains have been attributed partially to the iphone inefficiently pinging the network (icloud) . a network reset has done the trick for me in the past

 

[DrTek]

Still having issues with the Ringer and Haptics on the XS Max. Sometimes it works, sometimes it won't. Started after Beta 7.

 

[Mr$tone]

Anyone else getting each mail notification twice with latest Outlook (4.1.3) and iOS 13.1 beta 2?