A new build can still introduce bugs. Which is what happened here. We’ve seen this happen many years. It’ll be resolved. You’re making this out to be bigger than it is.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
All my office365 apps crash on iPadOS 15 RC
- Thread starter martinocando
- Start date
- Sort by reaction score
A new build can still introduce bugs. Which is what happened here. We’ve seen this happen many years. It’ll be resolved. You’re making this out to be bigger than it is.
I use iPhones since the initial release and I use betas since they were intriduced. There has never been a major change in a GM / RC. It is quite a big thing because we all know MS is rather on the slow end with bug fixes. And iOS15 will be released in 3 days. This will go all over the news if Office apps won't work on release day. And it will be a big issue for all those depending on it.
I’m making more of this? Wow.
I simply pointed out what is industry practice and also running a software business with 5 developers.
Bug fixes at this stage should not break an api. If it does then it’s piss poor quality control. If a bug fix causes a regression then it’s the same - poor quality control if this what happened.
When you fix a bug you go and re run all the tests and re verify your app still works.
I hope it’s not any of this and instead a server side verification issue. We will see.
You’re assuming an API has broken, when it could be any number of things. Which is not looking to be the case, in this instance.
I’ve seen things like this happen most years. If this is your first time it’s happened, lucky you.
it’s happened with some of the banking apps I use last year.
I wouldn't count banking apps into this because most are known for not running under a beta for good reasons.
While I agree with you for the most part, Office is not a banking app, which means that the user base is way larger that the customers of a specific bank in one country. This is a worldwide used app by many, not only personal users, but most corporations rely on Microsoft apps.
This kind of bug shouldn't have happened on an RC release.
Banking apps was just one example.
I’ve had many other apps have the same over the years, some were productivity apps, some social media apps.
The type of app was not relevant to my point, just supplementary.
My point is, I’ve seen it many times that an app broke with the RC. If you think it could never happen, you need to readjust your thinking.
It shouldn’t happen, but you can say that for many things. RC’s should be the final, but we’ve had RC2’s, which supports the fact that stuff happens and breaks when you’d not expect it.
No need to readjust my thinking. I never said could never happen, I said it shouldn't happen so late at this stage. I've also been beta testing for at least 8 years, and I remember all sorts of apps breaking during the beta testing, but not in the RC. At least none of the apps I used. Or my memory is not good enough.
I heard someone talking about an api change, or maybe the Office app was dependent on a temporary library that was used during testing and deprecated on the RC, who knows. We can argue for hours and not reach any solution, as is not in our hands. I think the point many people in this thread is making is that Microsoft should do better next time. Is not like it is some guy writing code in his couch, is Microsoft.
UPDATE: I installed the latest version from TestFlight and I can confirm that looks like the issue has been fixed. The first time I logged in with Outlook and ran the Office app it crashed, and I was about to be very upset, but then I ran it again, and is working with no apparent issues.
I'll get back with more information if I have any issues during the day, but for now, I guess case closed.
I'll get back with more information if I have any issues during the day, but for now, I guess case closed.
here are all testflight versions released this morning. tested all of them and they seem to work. Build numbers are identical
https://testflight.apple.com/join/hw76phYi >> word
https://testflight.apple.com/join/3lIiz1eZ >> excel
https://testflight.apple.com/join/a9Ef0N3g >> powerpoint
https://testflight.apple.com/join/3lIiz1eZ >> excel
https://testflight.apple.com/join/a9Ef0N3g >> powerpoint
My point is, yes it shouldn’t happen, that an RC breaks an app that worked under Beta 8, but it can and does happen. it’s nothing new. I’ve seen it many times with many apps, ever since the first App Store submissions
The main reason developers are given the RC is for them to check that nothing has broken between it & the last beta, and that’s why Apple don’t let Devs submit iOS 15 SDK updated apps until the day after the RC comes out.
As can be seen, MS have already fixed it and it will be coming out on Monday (extremely likely), just in time for iOS 15.
There were apps last year that got broken by the RC, and Devs got peeved at Apple, as they did the public release the following day, instead of the usual 1 week gap, so could be worse.
I was coming here to spread that good news, but didn’t realise it came out earlier, as was stuck in Chemo with no wifi 😠here are all testflight versions released this morning. tested all of them and they seem to work. Build numbers are identical
Excel update just available in App Store, they must be rolling out the fixed versions already. Seems to be working for my SSO accounts on iPad Pro and iPhone 12 Pro.
Looks like the fixed apps are rolling out in App Store now - excel and powerpoint updates out so far...
