The data couldn't be read because it isn't in the correct format.

Question

Level 1

10 points

The data couldn't be read because it isn't in the correct format.

I use an app called " Supa Legacy IPTV", and its ran perfectly up until I updated my iPhone 14 ProMax to IOS17. Now every time I try to log in I get this error. The app developers replied that the issue is with IOS17. Can you please tell me what I need to do to get this app working again? My Ipad hasn't been updated yet, and it still runs perfectly, so I don't understand what has changed in the IOS17 update.

iPhone 14 Pro Max, iOS 17

Posted on Sep 30, 2023 2:06 AM

Reply

Answer 1

Top-ranking reply

Micky_J_W

Level 1

8 points

Nov 11, 2023 2:51 PM in response to dee_lish

iCloud Private Relay was causing this problem for me.

switched it off, and SupaLegacy works perfect! 😃

settings, click your name, ICloud, Private Relay.

you can switch it off temporarily, or for good.

Hope that helps!

Reply

Answer 2

Rudegar

Level 10

181,632 points

Sep 30, 2023 2:16 AM in response to dee_lish

only the app developer can fix it, if apple changed something in ios that broke his app then he needs to update his app to work once more, it would be impossible that if third party apps broke when apple release a new ios version that apple had to keep making new ios updates to fix third party apps

Reply

Answer 3

Rudegar

Level 10

181,632 points

Sep 30, 2023 4:04 AM in response to dee_lish

just guess work, maybe they added encryption and the settings of the app you currently have issues with fail to be read because it's not encrypted who knows

This is a user helping users with tech questions forum, we are not apple and apple do not read your posts here

Get Support (apple.com)

And or

Contact - Official Apple Support

or give them feedback

Feedback - iPhone - Apple

Reply

Answer 4

dee_lish Author

Level 1

10 points

Sep 30, 2023 3:17 AM in response to Rudegar

why would apple change the way input data is read by an app? There are thousands of reports of the exact same problem with Mojave software when it was released to Mac's. Apple never intended for that problem to occur with Mojave. They noticed there was an issue and rectified it. Kind of feels like the same would happen now? Last time it was an issue with the Automatic Time clock. If its something as simple as that, just tell people how to fix it. Instead of ruining apps for people.

Reply

Answer 5

dee_lish Author

Level 1

10 points

Sep 30, 2023 4:25 AM in response to Rudegar

Yeah i get that, just thought that may be some supreme overlords that clearly have 10,000x my knowledge when it comes to apple lol. Ive only been here since iPhone 12's. Kinda waiting for someone to say " ahhh you idiot, its an easy fix just do blah blah blah". Always seems to be the way with apple lol.

Reply