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

Snapchat Aware of Latest App Store Update Causing App Crash, Promises Fix Soon [Updated]

Mr.Blacky said:
Snapchat has updated the App Store? I'm not familiar with Snapchat, does it have it's own App Store? I thought Apple are forbidding this?
Click to expand...

Yah, I've noticed this trend, too. Many of these article writers are using "new-age" writing without stepping back and thinking if what they just wrote makes any sense.

"... Latest App Store Update..."

Why was it important to inject "App Store" into that title?
 
zorinlynx said:
One of the biggest annoyances about the App Store is the inability to roll back to the previous version of an app.

I don't understand why Apple hasn't implemented such basic functionality. There's no reason a bad update should inconvenience users any longer than it takes for them to hit "Downgrade".
Click to expand...
Because when publishers fix exploits they don't want you to be able to use them. So sad by the way haha

now i see it said:
Not once in ten years have I ever found updating any app worth anything. The new version is never better, just different and usually worse in many respects. My motto: if you've got an app the works fine, DONT update it ever
Click to expand...
you are so right!!
 
scheinderrob said:
Rollbacks are very basic things about pushing new code. There should be a mechanism to backup any supporting files. In either case, your point is moot since the developer remains in full control of the decision to rollback.

You're the one who doesn't sound like a programmer. If you are one, you must be fresh out of college or not very experienced.
Click to expand...
Macbookfan was simply stating a possibility. Your response is insulting.

Sure software developers can build in rollback capabilities. Unfortunately that does not always happen. MacBookfan summarized well.
 
  • Like
Reactions: macbookfan
robjulo said:
There are 280 million daily users which is up 22% from the prior year.
Click to expand...
The poster was just trying to be cutesy and clever, neither of which was achieved. Questioning the existence of platforms that don’t meet some poster’s approval has become a cottage industry.

People still use Google?
People still use Apple?
People still use Twitter?
People still use Facebbok?
People still buy from Amazon?

Well, you get the picture. Old and tired.
 
  • Like
Reactions: justin0712
xStep said:
Macbookfan was simply stating a possibility. Your response is insulting.

Sure software developers can build in rollback capabilities. Unfortunately that does not always happen. MacBookfan summarized well.
Click to expand...
Again, it's the developers risk to take. It's really not that complicated.
 
  • Like
Reactions: Shirasaki
zorinlynx said:
One of the biggest annoyances about the App Store is the inability to roll back to the previous version of an app.

I don't understand why Apple hasn't implemented such basic functionality. There's no reason a bad update should inconvenience users any longer than it takes for them to hit "Downgrade".
Click to expand...
One of the 1000 developer tools developers have been calling for for years, but never ever get implemented.

It's what happens when you have no competitive pressure and need to work to retain developers.
 
  • Like
Reactions: Shirasaki
bgraham said:
One of the 1000 developer tools developers have been calling for for years, but never ever get implemented.

It's what happens when you have no competitive pressure and need to work to retain developers.
Click to expand...

It's not like you get all of these features even with competition. Look at Visual Studio and the Microsoft Store. Microsoft have spent years trying to get anyone to use it, still the store itself has been extremely featureless and lacklustre and there is no easy way for developers or users to downgrade their apps there either.
 
scheinderrob said:
Again, it's the developers risk to take. It's really not that complicated.
Click to expand...
It’s not that easy. Sometimes going live with an app upgrade means certain database upgrades as well that are hard to roll back without losing customer data for a set period of time, which is extremely damaging.

There are best practices and then there are what companies actually practice. Not everyone is equipped to do instant rollbacks, and sometimes it’s impossible depending on the architecture.

You post with the same confidence I used to have in my dev opinions before I realized how little of a fish we are in an ocean of technology that we don’t come close to understanding the majority of. It’s a humbling lesson that kicks in around 5 years practical experience, but I guess sometimes it doesn’t.
 
lkrupp said:
The poster was just trying to be cutesy and clever, neither of which was achieved.
Click to expand...
The poster was just posting for the sake of posting.

S/he's almost always one of the first 10, if not first 5, people to post a reply in a new front page story.
 
Absolute Trainwreck said:
It’s not that easy. Sometimes going live with an app upgrade means certain database upgrades as well that are hard to roll back without losing customer data for a set period of time, which is extremely damaging.

There are best practices and then there are what companies actually practice. Not everyone is equipped to do instant rollbacks, and sometimes it’s impossible depending on the architecture.

You post with the same confidence I used to have in my dev opinions before I realized how little of a fish we are in an ocean of technology that we don’t come close to understanding the majority of. It’s a humbling lesson that kicks in around 5 years practical experience, but I guess sometimes it doesn’t.
Click to expand...

I'm still waiting for a rebuttal to my argument.

App is currently nonfunctional. Devs make the decision to risk rollback or not.

If they are not equipped, then they can fix forward. Nobody is saying mandatory rollbacks.

Why is this so complicated for people here?
 
  • Like
  • Disagree
Reactions: Shirasaki and Absolute Trainwreck
it’s been fixed now. when i thought my entire week has been ruined, snapchat pushes out a fix. now i can rest happily. GO SNAPCHAT GO!!!!!!111!1!1!!1!
 
To all “developers” in this thread, Apple CERTAINLY can introduce a feature that allows users to install previous version of the app. They simply just store binary files (ipa) of previous versions for a limited time, and purge them after an update from dev or so. All they need to pay is storage cost.

Worst case scenario, apple can implement iOS in such a way that it will take a full snapshot (not the one in this article kekw) before updating, and store it locally. If user finds out their app not operating properly, they can revert back to that snapshot and risk minimal data loss if any. Apple can throw this setting somewhere deep, default off, and user has to turn on on an app by app basis.

TestFlight apps can roll back to previous build. Why release version can’t?
 
  • Disagree
Reactions: macbookfan
scheinderrob said:
Rollbacks are very basic things about pushing new code. There should be a mechanism to backup any supporting files. In either case, your point is moot since the developer remains in full control of the decision to rollback.

You're the one who doesn't sound like a programmer. If you are one, you must be fresh out of college or not very experienced.
Click to expand...
You are really really showing you didn’t think that through.

If you think every app developer out there is going to put in rollback for the app you are mistaken. A lot of the free apps are made by kids just learning to program. Apple could not rely on them to do it correctly.

So your solution would then be to keep a backup copy of all the data for the app after every update.

Taking the burden off the developer. This would be a horrible user experience. How about silent errors?

Example a diary app with a problem between two versions of the database. This could lead to silent errors where the app is deleting old data while the user is still creating new data. Now the user finally finds a couple weeks later they are missing old data and you expect them to do a rollback and loose all the new work they entered.

The only chance in hell Apple could pull it off is if they forced the uses of a specific database that they can control. Like CoreStorage. And any developer you ask will tell you how crappy that experience is.

in addition to all that think about all the extra storage needed.

think before you speak.
 
Shirasaki said:
To all “developers” in this thread, Apple CERTAINLY can introduce a feature that allows users to install previous version of the app. They simply just store binary files (ipa) of previous versions for a limited time, and purge them after an update from dev or so. All they need to pay is storage cost.

Worst case scenario, apple can implement iOS in such a way that it will take a full snapshot (not the one in this article kekw) before updating, and store it locally. If user finds out their app not operating properly, they can revert back to that snapshot and risk minimal data loss if any. Apple can throw this setting somewhere deep, default off, and user has to turn on on an app by app basis.

TestFlight apps can roll back to previous build. Why release version can’t?
Click to expand...
Snapshot only helps if it’s an immediately apartment issue like app crash . Silent errors can still exist and screw that data right up. Then the user has to choose between the new data entered and the old backup.

also a waste of space. Image a app with lots of media in its local storage like LunaFusuon. Or lots of images like DayOne.

also DayOne encrypts all it’s data. Same with most messaging apps. So it’s just one big blob. You are only going to have a restore everything or nothing at the OS level as it’s not going to understand the data inside

this is simply something that can’t be done at the OS level without a ton of trade offs that make it a headache for the user.
 
  • Disagree
Reactions: Shirasaki
macbookfan said:
You are really really showing you didn’t think that through.

If you think every app developer out there is going to put in rollback for the app you are mistaken. A lot of the free apps are made by kids just learning to program. Apple could not rely on them to do it correctly.

So your solution would then be to keep a backup copy of all the data for the app after every update.

Taking the burden off the developer. This would be a horrible user experience. How about silent errors?

Example a diary app with a problem between two versions of the database. This could lead to silent errors where the app is deleting old data while the user is still creating new data. Now the user finally finds a couple weeks later they are missing old data and you expect them to do a rollback and loose all the new work they entered.

The only chance in hell Apple could pull it off is if they forced the uses of a specific database that they can control. Like CoreStorage. And any developer you ask will tell you how crappy that experience is.

in addition to all that think about all the extra storage needed.

think before you speak.
Click to expand...


the choice is the developers, who know their own apps better than apple or you. im not sure where mandatory and automatic rollbacks are coming from, sounds like a fantasy in your head from your lack of programming experience.

it sounds like you need to take your own advice there at the end.

try again.
 
  • Like
Reactions: Shirasaki
macbookfan said:
Snapshot only helps if it’s an immediately apartment issue like app crash . Silent errors can still exist and screw that data right up. Then the user has to choose between the new data entered and the old backup.

also a waste of space. Image a app with lots of media in its local storage like LunaFusuon. Or lots of images like DayOne.

also DayOne encrypts all it’s data. Same with most messaging apps. So it’s just one big blob. You are only going to have a restore everything or nothing at the OS level as it’s not going to understand the data inside

this is simply something that can’t be done at the OS level without a ton of trade offs that make it a headache for the user.
Click to expand...

you have a shocking lack of of basic programming fundamentals. have you never heard of push scripts and rollback scripts for databases?

it sounds like you are equating your incompetency with all other developers.
 
  • Like
Reactions: Shirasaki
macbookfan said:
Snapshot only helps if it’s an immediately apartment issue like app crash . Silent errors can still exist and screw that data right up. Then the user has to choose between the new data entered and the old backup.

also a waste of space. Image a app with lots of media in its local storage like LunaFusuon. Or lots of images like DayOne.

also DayOne encrypts all it’s data. Same with most messaging apps. So it’s just one big blob. You are only going to have a restore everything or nothing at the OS level as it’s not going to understand the data inside

this is simply something that can’t be done at the OS level without a ton of trade offs that make it a headache for the user.
Click to expand...
1. I said this option is default off and user must enable it on an app by app basis. Some games also have their own data repair mechanism, so local backup is not necessary.

2. Yes, encrypted data becomes a huge blob from OS point of view. Isn’t iOS backup roughly the same thing? Instead of per app, it’s per device and has everything. Apple never officially introduce selective restore feature either for iCloud or for local backup.

3. This option at least can help some users to benefit somewhat by a backup, even though storing backup and actual data on the same storage media is a terrible idea.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back