iOS 12.3 Beta 3 ― Bug Fixes, Changes, and Improvements

Discussion in 'iOS 12' started by Banglazed, Apr 22, 2019.

Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.
  1. Banglazed, Apr 22, 2019
    Last edited by Banglazed: Apr 26, 2019

    Banglazed macrumors demi-god

    Banglazed

    Joined:
    Apr 17, 2017
    Location:
    Cupertino, CA
    #1
    iOS 12.3 Beta 3

    Release Date ― April 22, 2019
    Build Number ― 16F5139e
    Darwin Kernel Version ― 18.6.0: Thu Apr 18 19:45:13 PDT 2019; root:xnu-4903.260.85.0.2~1/

    iOS 12.3 Beta 3 Release Notes

    New Features & Changes

    New Issues
    Remaining Issues

    • iOS 12.3 beta 3 can only be installed if you are running iOS 12.3 beta 2. Our next beta release will resolve this issue so you can also install from other versions of iOS
    Resolved Issues
    • Resolved an issue that caused unexpected behavior while changing the system time ahead to May 1 when using a device with the system language and calendar set to Japanese
    • The Accessibility Events switch was removed, because related aspects of the W3C AOM effort are no longer applicable
    Additional Notes
    • Intel iPhone XR/XS/Max: 1.05.02
    • Qualcomm iPhone 8/8 Plus/X: 3.60.01
    • Intel iPhone 8/8 Plus/X: 2.03.06
    • Qualcomm iPhone 7/7 Plus: 5.60.01
    • Intel iPhone 7/7 Plus: 3.03.04
    • iPhone 6/6 Plus/SE: 7.70.01
    • iPhone 6S/6S Plus: 5.60.01
    • iPhone 5S: 10.70.01
    • Qualcomm iPad Pro 9.7: 5.60.01
    United States
    • Verizon - 36.0
    • Visible (MVNO Verizon) 34.0
    • Verizon (iPad) - 35.0
    • T-Mobile - 36.0.2
    • T-Mobile (iPad) - 34.5
    • AT&T - 36.0.2
    • Cricket - 35.5.3
    • MetroPCS -
    • U.S. Cellular - 32.5.9
    • Sprint - 36.0
    • TracFone/Straight Talk/Walmart Family Mobile - 36.0.2
    • Xfinity Mobile 35.5.1
    United Kingdom
    • EE - 36.0.1
    • BT-UK MVNO on EE- 36.0.1
    • Three - 36.0
    • O2-UK - 36.0
    • Vodafone UK - 36.0
    • Virgin Mobile MVNO on EE- 34.0
    Belgium
    • Orange B - 32.5.7
    • BASE - 33.0
    Canada
    • Videotron -
    • Rogers - 36.0.1
    • Fido - 35.5
    • Bell - 35.0
    • Telus - 32.5.12
    • Freedom Mobile - 34.0
    France
    • Orange France - 31.5.1
    • Orange Morocco - 31.5
    Germany
    • O2-DE - 36.0
    • Vodafone.de - 36.0
    • Telekom.de - 36.0
    Netherlands
    • KPN -
    Southeast Asia
    • Singapore Singtel -
    • Philippines Globe - 36.0
    • Philippines Globe (iPad) - 36.0
    • Philippines Smart - 36.1
    • Thailand AIS -
    • Malaysia Umobile - 33.0
    • Malaysia Maxis -33.0
    • Malaysia Digi -
    • Malaysia celcom -
    • Hong Kong - 32.0
    Sweden
    • Comviq -
    • Tre - 31.0
    Switzerland
    • Salt - 35.5
    • Swisscom - 35.0
    Ireland
    • Eir - 33.5
    Australia
    • Optus - 32.0
    • Telstra - 36.0
    Turkey
    • Turkcell (Lifecell) - 32.0
    • Vodafone TR - 32.0
    • Turk Telekom - 32.0
    Poland
    • T-Mobile -
    • Orange - 32.0
    • Play - 31.0
    India
    • Airtel - 35.0
    • Jio - 36.0
    • Vodafone Idea - 35.5
    Mexico
    • Mexico - Telcel - 35.0
    Guatemala
    • TIGO GT -34.0
    OtherDocomo - 32.5.10
    • AlwaysOnline -
     
  2. johnyslats macrumors 6502a

    johnyslats

    Joined:
    Mar 14, 2012
    Location:
    Leeds, UK
  3. FriendlyPanda macrumors regular

    FriendlyPanda

    Joined:
    Mar 11, 2019
    Location:
    California
  4. dannyyankou macrumors G3

    dannyyankou

    Joined:
    Mar 2, 2012
    Location:
    Scarsdale, NY
    #4
    It’s bigger than beta 2, that was like 350 mb or something.
     
  5. newtestleper macrumors 6502

    Joined:
    Jun 17, 2013
    #5
    The official obligatory “Thanks, Banglazed” post.
     
  6. Yun0 macrumors 65816

    Yun0

    Joined:
    Jun 12, 2013
    Location:
    Winnipeg, Canada
    #6
    Which means absolutely nothing.. an a build can be buggier than an f build and vice versa.
     
  7. FriendlyPanda, Apr 22, 2019
    Last edited: Apr 22, 2019

    FriendlyPanda macrumors regular

    FriendlyPanda

    Joined:
    Mar 11, 2019
    Location:
    California
    #7
    It doesn't mean absolutely nothing. There's a reason why later builds in a beta cycle have 'a' and 'b' tags on the build number as opposed to 'd' and 'e' on earlier builds.

    Personally, I'd rather run a more stable 'a' or 'b' build than one that has gone through multiple patches and fixes after being built.
     
  8. TimFL1 macrumors 6502

    Joined:
    Jul 6, 2017
    Location:
    Germany
    #8
    This. I'd pick the f build over the a build any day, potentially the more stable build due to several iterations of QA.
     
  9. Gregnyrfan macrumors member

    Gregnyrfan

    Joined:
    Jun 17, 2011
    #9
    iphone 6s Plus updates:
    ATT carrier: 36.0.2
    Modem Firmware: 5.60.01
     
  10. MrGimper macrumors 603

    MrGimper

    Joined:
    Sep 22, 2012
    Location:
    Andover, UK
  11. johnyslats macrumors 6502a

    johnyslats

    Joined:
    Mar 14, 2012
    Location:
    Leeds, UK
    #11
    Managed to get it 30 mins ago
     
  12. MrGimper macrumors 603

    MrGimper

    Joined:
    Sep 22, 2012
    Location:
    Andover, UK
    #12
    Thanks, just removed and reinstalled the beta profile and it's picked it up
     
  13. alecc131 macrumors regular

    Joined:
    Nov 13, 2013
    #13
    One change in the TV app (... I think it's a bug).

    In the Sports tab, tapping any of the events on the top, opens the corresponding app (e.g. Spectrum, DTV Now)... Even though the event does not start for several hours.

    When 3D touching these events, to add to up next. The UI for Share and Add To Up Next does not display. Instead, a blank template is displayed. This must be a bug.

    Also, another change.
    Tapping any currently "live" sports event, opens the app with the live event, rather than the page for the event in the TV app. This is a change from prior versions, where the page would first open in the TV app for the event, rather than directing straight to the event.
     
  14. BarrettF77 macrumors regular

    BarrettF77

    Joined:
    May 24, 2015
    #14
    I do wish the public betas would accompany the dev betas. Typically they do them together. I’ve found that beta 2 was a little sluggish in animations on the XS Max.
     
  15. TimFL1 macrumors 6502

    Joined:
    Jul 6, 2017
    Location:
    Germany
    #15
    They usually stagger public beta launch to check if any game breaking bugs show up in the developer beta. Kind of a smart thing to do, considering the people hopping onto the latest beta 24/7.
     
  16. brianld, Apr 22, 2019
    Last edited: Apr 22, 2019

    brianld macrumors regular

    brianld

    Joined:
    Jul 8, 2008
    Location:
    Seattle
    #16
    New to this build, Safari on iPad keeps crashing every time I try to manually type in an address (such as forums.macrumors.com).
     
  17. john991 macrumors 68000

    Joined:
    Sep 30, 2014
    Location:
    Ontario
    #17
    Happens on my iPhone too.
     
  18. BarrettF77 macrumors regular

    BarrettF77

    Joined:
    May 24, 2015
    #18
    Normally I'd agree with you on this, however, the level of stability that existed in 12.2 final release was so much less stable than the betas it wasn't even close to funny. I wish the HomePods could get on betas but sadly they cannot. I've lost a lot of confidence in Apple software stability in the last 5 weeks following the 12.2 public release and dealing with their support staff in whole.
     
  19. FriendlyPanda macrumors regular

    FriendlyPanda

    Joined:
    Mar 11, 2019
    Location:
    California
    #19
    Can confirm this happens on iPhone XS with 12.3 Beta 3.

    Didn't occur in Beta 2. Looks like Apple slipped a little bit with this new "e" build.
     
  20. newtestleper macrumors 6502

    Joined:
    Jun 17, 2013
    #20
    Not so on my XR.
     
  21. zorinlynx macrumors 603

    zorinlynx

    Joined:
    May 31, 2007
    Location:
    Florida, USA
    #21
    The second message I quoted is the reason for the first message I quoted. :)

    You don't want system breaking bugs like this to get out to the masses. Public beta has become very popular and you just KNOW people will go to the Apple Store to complain about bugs like these. Even if the store can say "tough ****, it's a beta" they still have to deal with these annoyed customers and it's bad for Apple's reputation.
     
  22. TimFL1 macrumors 6502

    Joined:
    Jul 6, 2017
    Location:
    Germany
    #22
    Game breaking bugs as in literally bricking your device, rendering them unusable (not general stability). We had a few of these over the years, Apple is usually quick to act (pulling defective versions) but imagine the outcry when a public beta build on potentially thousands of non-developer primary devices causes soft bricks.
     
  23. s2mike macrumors 6502a

    Joined:
    Sep 14, 2015
    #23
    I’m not experiencing the Safari crashes on my XS.

    For those who are experiencing it - have you tried force quitting safari and doing a hard restart?
     
  24. BarrettF77 macrumors regular

    BarrettF77

    Joined:
    May 24, 2015
    #24
    I work in IT software development as a PM and see this all the time where Agile is used and you sufficiently QA a release before pushing it out. Apple in public releases of late have not sent the final version out ahead in beta to "keep new products underwraps" which in turn messes up with stability. See the new Beats Pro headphones.
     
  25. FriendlyPanda macrumors regular

    FriendlyPanda

    Joined:
    Mar 11, 2019
    Location:
    California
    #25
    Yes, it's a new bug introduced in Beta 3.
     
Thread Status:
The first post in this thread is a WikiPost, and can be edited by anyone with the appropriate permissions.

Share This Page

240 April 22, 2019