Blorp

135 readers

1 users here now

This community has been moved to !blorp@lemmy.zip

founded 8 months ago

MODERATORS

moseschrute@lemmy.ml

RmDebArc_5@piefed.zip

moseschrute@lemmy.world

Any login issues on v1.9.11? (Edit, resolved) (lemmy.ml)

submitted 2 months ago* (last edited 1 month ago) by moseschrute@lemmy.ml to c/blorp@lemmy.ml

5 comments fedilink hide all child comments

Someone raised an issue with login, but I’m not sure if it’s login in general or to their specific instance. Anyone noticing any issues on version 1.9.11?

I’m not personally seeing an issue with login, but logout seems to crash the app. But I’m more concerned about login.

Regardless, this makes me think the next version should be purely focused on bug fixes and stability with no new features.

Edit: the bug only seems to happen when logging into a PieFed account with an unverified email address.

you are viewing a single comment's thread
view the rest of the comments

[–] moseschrute@lemmy.ml 1 points 1 month ago* (last edited 1 month ago) (1 children)

Edit: I think I might know the issue. Can you try v1.9.14 on TestFlight? Might take a couple hours to show up.

Yikes, this sounds like a not fun one. I saw a similar issue the other day on my phone, but reinstalling the app fixed it. I really hope I didn't break it with v1.9.12.

Would you mind making a post mentioning as much detail as you're comfortable sharing? iOS version, app version, and screenshots if you are comfortable. Maybe someone else is seeing a similar issue.

Another idea:

Delete Blorp. Make sure you fully delete before downloading form TestFlight.
Join TestFlight
Look for v1.9.14 on TestFlight

[+] Chrysanthemum@piefed.social 1 points 1 month ago (1 children)

[deleted]

[–] moseschrute@lemmy.ml 2 points 1 month ago (1 children)

Ok, between this and a bunch of other things, I think my choise of database within the app is a mistake. Initially I chose this database to prevent the dreaded Voyager There was an issue setting up Voyager's database. But at this point, think I’ve created a worse user expierence than just showing a similar error.

I’m going to gut the overly comples database I setup, and if we run into that database error, we will deal with it.

So a few things will happen:

Existing user data will be errased :(
Potentially the app may need to be relaunched form time to time. We’ll cross that bridge
This should simplify things pretty significantly so I can focus on building featrues instead of debuging database errors
This circumvents the whole security thing I ran into the other day

Idk if any of taht makes sense. I’m mostly thinking out loud