Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Banglazed

macrumors 603
Apr 17, 2017
5,005
9,478
Cupertino, CA
  • Like
Reactions: Pearsey and Ansath

chillip

macrumors 68040
Mar 16, 2013
3,248
2,853
The instruction is posted in the release/beta thread to install via IPSW in the wiki post. You will need a mac and free developer account. You can also try to install the MobileDeviceDevelopment.pkg as well to try. I've already set up my 15 and wouldn't want to restore it again.

Thanks, I will just leave it on the beta train for now. Runs well enough despite the touch screen issues. Are you on 17.1 beta?
 

gank41

macrumors 601
Mar 25, 2008
4,350
5,022
Beware on 17.1, you can’t restore back to 17.0.2. Trust me I have tried all the tricks. It’s a bug!

No going back now!

back-to-the-future-doc-brown.gif
 
  • Haha
  • Like
Reactions: Pearsey and Brad7

Realityck

macrumors G4
Nov 9, 2015
11,414
17,205
Silicon Valley, CA
Yes, if you bought a brand new a few days old iPhone 15, you really only have two choices, the obvious update to 17.0.2 immediately and wait for more fixes, or try 17.1 beta as another option see if it improves something not working correctly with 17.0.2. It neither isn't perfect enough, just waiting for the next 17.1 beta will arrive anywhere from 5 to 7 days from now. Both 15.1 and 16.1 were updated weekly. IMHO Its more likely you see see a 17.1 beta 2 before a 17.0.3 as that has a distinct beta cycle progression then the public releases. :)
 
Last edited:
  • Like
Reactions: redbeard331

chillip

macrumors 68040
Mar 16, 2013
3,248
2,853
Yes, if you bought a brand new a few days old iPhone 15, you really only have two choices, the obvious update to 17.0.2 immediately and wait for more fixes, or try 17.1 betaas another option see if it improves something not working correctly with 17.0.2. It neither isn't perfect enough, just waiting for the next 17.1 beta will arrive anywhere from 5 to 7 days from now. Both 15.1 and 16.1 were updated weekly. IMHO Its more likely you see see a 17.1 beta 2 before a 17.0.3 as that has a distinct beta cycle progression then the public releases. :)

Yeah hoping for beta 2 next week. Can’t go back to 17.0.2 anyway. Just want a fix for the touch lag.
 

MrRom92

macrumors 65816
Sep 30, 2021
1,122
2,376
Apple had plenty of time to issue another update. 1+ week is shameful with this many unacknowledged issues on a brand new flagship device. I no longer have anytime to update. I gave them more than enough opportunity. As of now I am sticking with 14 Pro Max on iOS 16 as I require a dependable device. I would personally not be shocked if a great number of people decided to return their iPhone 15s and 15 Pros within the 14 day window
 

MozMan68

macrumors 603
Jun 29, 2010
6,152
5,261
South Cackalacky
Apple had plenty of time to issue another update. 1+ week is shameful with this many unacknowledged issues on a brand new flagship device. I no longer have anytime to update. I gave them more than enough opportunity. As of now I am sticking with 14 Pro Max on iOS 16 as I require a dependable device. I would personally not be shocked if a great number of people decided to return their iPhone 15s and 15 Pros within the 14 day window

Maybe I missed something?

What’s wrong with the 15’s on current software??
 

MrRom92

macrumors 65816
Sep 30, 2021
1,122
2,376
I would say touchscreen issues on a touchscreen device probably shouldn’t be dismissed as insignificant. Don’t also forget botched ringtones and notification sounds, batteries that don’t charge the phone, CarPlay that doesn’t work, HomeKit Intercom nonfunctional, overheating issues and throttling processors, USB-C data transfer on the pro still limited to USB 2.0 speeds on Windows PCs. What else am I forgetting?
 

gwhizkids

macrumors G5
Jun 21, 2013
13,307
21,484
I would say touchscreen issues on a touchscreen device probably shouldn’t be dismissed as insignificant. Don’t also forget botched ringtones and notification sounds, batteries that don’t charge the phone, CarPlay that doesn’t work, HomeKit Intercom nonfunctional, overheating issues and throttling processors, USB-C data transfer on the pro still limited to USB 2.0 speeds on Windows PCs. What else am I forgetting?

I guarantee you that these individual issues happen to a very small subset of one billion users worldwide. And not all to any one person.

Thus, despite the possible severity to a particular iPhone user who may experience them, they are indeed statistically insignificant.
 

gwhizkids

macrumors G5
Jun 21, 2013
13,307
21,484
Apple Pay and Bluetooth not working. The Pros are overheating. Build quality issues with the titanium.

Yes. The titanium issues should be addressed by Apple’s 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 engineers ASAP. I’m sure they’re all over it.

Bottom line: don’t take issues you see raised in these forums as typical. In many cases they are not. And Apple is not going to chase down issues (that may not even be their software’s fault) that affect a minuscule number of users, no matter how vocal they are.
 
  • Like
Reactions: blueeyes2die4

MrRom92

macrumors 65816
Sep 30, 2021
1,122
2,376
Yes. The titanium issues should be addressed by Apple’s 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 engineers ASAP. I’m sure they’re all over it.

Bottom line: don’t take issues you see raised in these forums as typical. In many cases they are not. And Apple is not going to chase down issues (that may not even be their software’s fault) that affect a minuscule number of users, no matter how vocal they are.

I am hearing/reading about these issues from all manner of people offline and online, and there are many more I neglected to mention. Doesn’t take more than a cursory glance through the iOS 17 forum to see that. But sure let’s just minimize all of that and pretend that iOS 17 is flawless.
 

gwhizkids

macrumors G5
Jun 21, 2013
13,307
21,484
I am hearing/reading about these issues from all manner of people offline and online, and there are many more I neglected to mention. Doesn’t take more than a cursory glance through the iOS 17 forum to see that. But sure let’s just minimize all of that and pretend that iOS 17 is flawless.

Who said it was flawless? Certainly not me.

Everything you say may be true in your world. But anecdotal evidence is essentially worthless.

Of course you’re going to see complaints in the forums. That’s what people come here to do. Who wants to read 100s of people saying “my phone is fine”? Sensible people realize that and don’t post that or don’t ever come to the forums in the first place. That’s why I don’t rely heavily on Amazon reviews, for example. Happy customers don’t post reviews as frequently.

There might be a million people out there with any particular problem. But that’s 1/10th of 1% of the user base. No company is going to use precious resources to deal with that small a universe of affected users.

And, as I noted above, many of these problems may be due to the unique setups of the user. Corrupt backups being used following upgrades, prior jailbreaking, hardware issues, unusual app configurations, you name it, they can all cause problems unrelated to the base software integrity.
 

Realityck

macrumors G4
Nov 9, 2015
11,414
17,205
Silicon Valley, CA
Just 3 - 4 days away from 7.1 beta 2 which might work better for some that experienced issues with their unique app/configuration usages using the latest devices. Bear with it guys. ;)
 
  • Like
Reactions: Pearsey

Realityck

macrumors G4
Nov 9, 2015
11,414
17,205
Silicon Valley, CA
Could be a 2 week schedule 😐
Neither the previous 15.1 or 16.1 were that, both were the same as the SDK notes show a few specific bug fixes.

Remote Widgetsin page link

Resolved Issuesin page link

  • Fixed: Remote Widgets might render blank on mismatched iOS and macOS releases. (115436466)

SKAdNetworkin page link

Resolved Issuesin page link

  • Fixed: Calling the deprecated SKAdNetwork registerAppForAdNetworkAttribution API will not reset the conversion value to 0 in SKAdNetwork 4.0 postbacks. (113371209)

Wallet & Apple Payin page link

Known Issuesin page link

  • Users will need to select bank accounts link to Wallet on a per-issuer basis. Subsequent connections with the same issuer overwrite the previous connection. (107258608)
  • Customers are unable to link their bank account to a card in Wallet from Settings. (108505644)
    Workaround: Start the connection flow in Wallet.
  • The transaction icon for ACH Transfers is not localised from “$” to currency of the account. (110706635)
  • Users might not be able to relink their bank account to a card in Wallet if the connection was unexpectedly disconnected. (112409556)
  • Titles and descriptions of transactions might not display after update. (113845510)
    Workaround: Close and re-open Wallet.
  • Foreign currency transactions on cards linked to bank accounts might incorrectly swap Local Amount and Total amount. (114187393)
  • Order Tracking details might unexpectedly disappear from the transaction details of cards linked to bank accounts. (114253102)
    Workaround: View your order details by navigating to Wallet > Orders.
  • In the Settings pane for Wallet & Apple Pay for cards linked tobank accounts, negative balances in your card’s balance history might display as positive. (115171512)
  • During the process of linking a bank account to a card to Wallet, the UI might unexpectedly display Light Mode when in Dark Mode. (115174273)

WidgetKitin page link

Known Issuesin page link

  • In widgets Text(_:style doesn’t animate its content by default. (107582710)
    Workaround: To explicitly request an animation, use the View.contentTransition(_ modifier.
 
  • Like
Reactions: Pearsey and gank41
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.