The devRant app just crashed after writing a 4000+ character rant on my fucking phone.

Fuck me.

LONG RANT AHEAD!

In my workplace (dev company) I am the only dev using Linux on my workstation. I joined project XX, a senior dev onboarded me. Downloaded the code, built the source, launched the app,.. BAM - an exception in catalina.out. ORM framework failed to map something.

mvn clean && mvn install

same thing happens again. I address this incident to sr dev and response is "well.... it works on my machine and has worked for all other devs. It must be your environment issue. Prolly linux is to blame?" So I spend another hour trying to dig up the bug. Narrowed it down to a single datamodel with ORM mapping annotation looking somewhat off. Fixed it.

mvn clean && mvn install

the app now works perfectly. Apparently this bug has been in the codebase for years and Windows used to mask it somehow w/o throwing an exception. God knows what undefined behaviour was happening in the background...

Months fly by and I'm invited to join another project. Sounds really cool! I get accesses, checkout the code, build it (after crossing the hell of VPNs on Linux). Run component 1/4 -- all goocy. run component 2,3/4 -- looks perfect. Run component 4/4 -- BAM: LinkageError. Turns out there is something wrong with OSGi dependencies as ClassLoader attempts to load the same class twice, from 2 different sources. Coworkers with Windows and MACs have never seen this kind of exception and lead dev replies with "I think you should use a normal environment for work rather than playing with your Linux". Wtf... It's java. Every env is "normal env" for JVM! I do some digging. One day passes by.. second one.. third.. the weekend.. The next Friday comes and I still haven't succeeded to launch component #4. Eventually I give up (since I cannot charge a client for a week I spent trying to set up my env) and walk away from that project. Ever since this LinkageError was always in my mind, for some reason I could not let it go. It was driving me CRAZY! So half a year passes by and one of the project devs gets a new MB pro. 2 days later I get a PM: "umm.. were you the one who used to get LinkageError while starting component #4 up?". You guys have NO IDEA how happy his message made me. I mean... I was frickin HIGH: all smiling, singing, even dancing behind my desk!! Apparently the guy had the same problem I did. Except he was familiar with the project quite well. It took 3 more days for him to figure out what was wrong and fix it. And it indeed was an error in the project -- not my "abnormal Linux env"! And again for some hell knows what reason Windows was masking a mistake in the codebase and not popping an error where it must have popped. Linux on the other hand found the error and crashed the app immediatelly so the product would not be shipped with God knows what bugs...

I do not mean to bring up a flame war or smth, but It's obvious I've kind of saved 2 projects from "undefined magical behaviour" by just using Linux. I guess what I really wanted to say is that no matter how good dev you are, whether you are a sr, lead or chief dev, if your coworker (let it be another sr or a jr dev) says he gets an error and YOU cannot figure out what the heck is wrong, you should not blame the dev or an environment w/o knowing it for a fact. If something is not working - figure out the WHATs and WHYs first. Analyze, compare data to other envs,... Not only you will help a new guy to join your team but also you'll learn something new. And in some cases something crucial, e.g. a serious messup in the codebase.

string excuses[]={
"it's not a bug it's a feature",
"it worked on my machine",
"i tested it and it worked",
"its production ready",
"your browser must be caching the old content",
"that error means it was successful",
"the client fucked it up",
"the systems crashed and the code got lost" ,
"this code wont go into the final version",
"It's a compiler issue",
"it's only a minor issue",
"this will take two weeks max",
"my code is flawless must be someone else's mistake",
"it worked a minute ago",
"that was not in the original specification",
"i will fix this",
"I was told to stop working on that when something important came up",
"You must have the wrong version",
"that's way beyond my pay grade",
"that's just an unlucky coincidence",
"i saw the new guy screw around with the systems",
"our servers must've been hacked",
"i wasn't given enough time",
"its the designers fault",
"it probably won't happen again",
"your expectations were unrealistic",
"everything's great on my end",
"that's not my code",
"it's a hardware problem",
"it's a firewall issue",
"it's a character encoding issue",
"a third party API isn't responding",
"that was only supposed to be a placeholder",
"The third party documentation is wrong",
"that was just a temporary fix.",
"We outsourced that months ago.","
"that value is only wrong half of the time.",
"the person responsible for that does not work here anymore",
"That was literally a one in a million error",
"our servers couldn't handle the traffic the app was receiving",
"your machines processors must be too slow",
"your pc is too outdated",
"that is a known issue with the programming language",
"it would take too much time and resources to rebuild from scratch",
"this is historically grown",
"users will hardly notice that",
"i will fix it" };

I JUST WROTE A 2000 CHARACTER RANT AND THE DEVRANT APP CRASHED

>:((((( ANGERY

Ah, let me open my half baked personal Android project. Maybe I'll finish it this time.

*opens Android studio*

"You have shitloads of updates. Please download and restart now"

Ok, makes sense. I haven't opened it for a month.

*runs the app*

"CoolApp has crashed"

What the fuck? It was all working before. WTF happened.

*half an hour of online research*

The google play service version is somehow fucked up. So let's fix that.

*App opens*

Yay! Let me login right away!

*Login via google doesn't work*

I didn't even touched the bloody code.

*another half an hour of research. Nothing works*

Fuck this shit.

Designer: Need to file a bug, I'm not getting an option to login with FaceID

Me: Oh weird bug. Is it setup on the phone you are testing with?

Designer: yes, use it in all other apps

Me: Did you get an error during onboarding on the FaceID screen?

Designer: nope no error

Me: ..... hhhmm, can you show me your settings?

Me: ... eh, says you have FaceID disabled for this app ... did you click "No" to FaceID during onboarding?

Designer: Yes, to test edge cases

Me: ................ ok ........ if you setup the app and told it to not allow FaceID to login ......... you won't get the ability to use FaceID to login .......... like .... by design .... on purpose ...... cause .... you told it to do that

Designer: No no, it needs to have a setting on the login screen to allow me to turn that back on incase I forget my passcode

Me: the fuck it does. Yeah we can't have anything on the login page that says, without authorization, change my settings

*Deep breath*

Me: Remember we had this conversation previously, where you didn't want the user to create a passcode during onboarding as it was too much friction, and wanted to do FaceID only. With your backup plan being to allow the user to create a NEW passcode on the login screen if FaceID failed .... remember that discussion we had about security? ... and how its important? ... and that we like having any? Ok so its the same reason as that, just with a different setting this time

Designer: ... hhmm i'm not sure I like this

Me: ... tough luck then, not happening

Me: oh and btw, remember we had that other talk about reproduction steps for bugs? Like when the app crashed and you told me it was because its in light mode, and nothing else at all? So disabling FaceID, is very relevant info to the problem of "I can't login with FaceID", please tell me these things first

Made a web app at work.

Client reported the site crashed​ IE10 when it loaded.

I'm not even sad about it XD

DEVRANT CRASHED AND MY RANT IS GONE! I'M NOT A HAPPY MISH.

To be brief, I just remembered how my father used to smash my phone to the ground when he was angry about it.

Everytime he sees me using it. Smash!

I once made a Facebook to make more friends since I didn't have much, and still don't. (I didn't use the app btw.) He saw my search history and was furious. (My parents don't permit me to have social media. They think devRant is a school thing.)

He smashed it to the ground saying I can never use Facebook again.

He did that to 3 phones.

Fortunately, he doesn't do that anymore. Mainly because I'm the one who helps him with computer stuff and searches for the emails he needs.

Mobile app crashed a lot after latest release. Everyone called for a meeting to discuss the issue and find resolutions.

Engineering lead for backend team: well part of our problem is we haven’t had time to test everything fully. Maybe product could give us a list of all the features that can’t go down and we’ll prioritize those for testing?

Product: ... ... ... all of them?

Me: laughing hysterically while on mute

Previous developers read entire result of a SELECT into array of arrays.

Then used that later on in the following fashion.

print "name: " + result[row][17]
print "address: " + result[row][23]
...
without any description whatsoever what the numbers mean.

And it's here "result" and "row", in the actual code it was "arr" and "ii".

And these arrays were "public static" used everywhere, but initialized only at few places, so if you went onto wrong screen or if there was a phone call that kicked the app out it crashed.

But real fun began when people started changing queries and altering tables...

I seriously thought I was being pranked as a new hire.

FUCK!

I just finished a 3500 characters rant. Was typing a tag and the app crashed!

FOR FUCK SAKE APPLE! HOW THE HELL ARE YOU STILL IN THIS WORLD!

Was creating a signed file of the app to upload to their store and while XCode (that bitch!) was working on it, Slack, and Postman crashed!
Do I need to say why or you already knew it is because XCode ate all the RAM -.-

It's always fun when the app is crashed by a... logger

OKAY FUCK OFF APP I JUST WROTE A LONG AF STORY AND THE DEVRANT APP WENT AND CRASHED

i guess i will write the story some other time then :).

I was once using an app, made by my friend which could be used as a handy reference for programming topics. It crashed every time i clicked the last entry of the list. I told him that the app has a bug, probably some position mistake and he denied, saying that he doesn't need feedback from a guy who didn't code applications. I learned to code java and started android that night and knew I needed to give him a reply, a good one.

After spending around 8+ hours on an Adobe After Effects project (which I obviously didn't save), at around 12 at night, it crashed.

I lost everything. Was heartbroken. Died inside. Nearly cried. Then I restarted the app and started from scratch.

The weird thing is I recreated the entire thing in around 1.5 hours. Not sure if I'm happy or sad with myself.

This happened a few weeks ago at school.

The previous semester we had to work in a group to make a basic Android application. After handing it in to the teacher, we had to present it in front off the class.

During this project, one of the groups was having some problems with a member, mainly because of misunderstandings and miscommunication. He definitely has technical skills, but he really needs to work on his focus and communicational skills.
The member was removed from the group and had to do it on his own. He had 2 days to make the app, which we initially got 2 weeks for.

Skip forward to presentation day.
Every group presented their app and got feedback from the teacher and the rest of the students.

Lastly, the guy that was on his own was giving his presentation. He started his powerpoint and explained what happened during the project and what went wrong. Then he said: "This is a black page in my school career, everything that could have gone wrong, went wrong". Immediately after saying this, he proceeds to go to the next slide: His laptop crashed, Blue Screen Of Death.

This was one of the most painful moments I've ever witnessed during a presentation.
I couldn't believe the timing of Windows to fuck up.

Designer reporting a UI/Design related bug:

I noticed the wrong colour is being used on screen X. It should be xxxxx. Its imperative that we fix this, as it destroys the entire design motif. Our colour scheme draws influence from the ancient Mayans. They were relentless in their pursuit of excellence, whether it be their temples, their sophisticated writing system, their complex calendars, or their advanced mathematics.They sought immortality through their work, as do we with ours. Users will become lost in our onboarding unless we harmonise the flow, the slightest deviation could be catastrophic. Please fix this as priority 1, to avoid running the balance of the app

Designer reporting a technical bug:

Oh yeah, app crashed last week. Not sure what I was doing, maybe look into that

App crashed during a live demo. Hard not to feel bad especially since it's friday and i have to go into the weekend with that thought. Am i overreacting?

Noticed a new version of our primary customer management application was deployed to my machine. Its been a while since I've seen it, so I decide to see all the 'improvements' over the 'old' one (~18 year old app written in Delphi).

Wow, it's slow, several seconds to open. Tried to open my account..really, really slow.

Notice a lonely edit box with no label, and button right next to it with no caption, so I click it and get the attached error.

Tried to place an order, I must have done something 'out of sequence' because I clicked another button and the whole app crashed.

In less than 5 minutes I found a dozen or so UX failures. I suck pretty bad at UI, but good lord...what the frack happened to basic usability.

Idk if I'm happier about the usability of the app or the image notifications with the not-yet-crashed background activity or the super cute anime wallpapers but the thing works and looks pretty xD what else could you want from a minor side project :')

Hard drive head crashed and corrupted my entire android app source code which took my 5 months to build. I was depressed for 2 days and then started working for it again and updated the app on the store in 3 months. It was a terrifying yet amazing experience. Definitely don't want to go through that again.
Now I keep backups on the cloud. Lesson learnt.

Sorry, I crashed the app!

Tried to open 'Recent App Crashes' tab in the Google Play Console app. Play Console crashed. Thanks Google.

Deployed new app server at night for a number of prime client companies

It crashed at peak hours

Backend API developer that doesn't admit his mistakes. Damn, he's annoying the whole team.

Basically crashed the whole app by messing up the settings for the CORS policy, and still doesn't admit it. When he fixed it, the only reply we get was "I erased the thing and put it back and it works".

WOW!

My app crashed in production and there's nothing in in the error logs..

Yay..

I didn't posted something in a long time so...

TL;DR: FUCK YOU ANDROID STUDIO YOU FUCKING SHIT PIECE OF SOFTWARE

Thank you for your time.

I am running my own meme social network. For quite some time I wished I knew a Android developer, which could help me.

Because I know java I tried it myself, and Android studio is one of the worst programms I've ever seen.

My app crashed the whole time, just because my studio version was 1 behind. Updated studio, everything worked.

My layout wasn't showing correctly, reopened Studio, all layouts deleted.

For no good reason video views aren't resizing, so I need to use exoplayer.

One video on my platform nearly crashes the app when creating a thumbnail.

And so one....

I fucking hate Android studio...

(PS: if your a German, Swiss, Austrian you could check out my network and may become a beta tester of the app)

Follow up to previous rant:

Now after I realised that I'm a stupid motherfucker, today was release day. Or so it was planned.
Because turned out my colleagues/supervisors didn't tell me to test the app on Android 6 devices and I was sure that if it ran on the device they gave me (which I assumed was the only device of our clients) it'd be sufficient.
Now it was tested on an android 6 device and crashed constantly.
Wow... I mean... Just wow... Now because I don't have a working android 6 device (a colleague of mine is on vacation and locked our development devices for a different app into a drawer) I have to get the emulator working which took me about 2 hours because that dumb shit face of a laptop first didn't have the android-sdk-root set (took me a good hour to realise) and then the kernel for the avds was missing.
Also: windows updates.
FUUUUUUUUUUUU....

(PS: yeah I should have tested it on various devices and made sure it worked on at least most of them without being told so. Another example for my stupidity.)

EDIT: Now I don't have enough disc space for the kernel I need to install. Absofuckingfantastic

Don't you love it when you're in a full-on creative mood but the whole universe is somehow working against you doing anything productive?

Woke up in the morning with bright ideas for my app. But my PC restarted and my IDE crashed. After getting the IDE up, the project no longer builds. After spending hours to try and fix it, reinstall IDE and ............... voila............... everything works. I mean WTF?

Was recently asked if our team wanted to change from Java to Kotlin so I looked over the feature lists but don't see much that's impressive.

One argument was less boilerplate code but I think they're are libraries like Lomboq that can write that stuff for you.

The other was smart type casting and type inference and to that I'm like this sounds like giving monkeys a hammer.

Our JS codebase looks like shit... And our Java app just crashed in prod.

Getting a ton of text messages this morning and thankfully I'm on vacation still...

The error is not caused by NPE... but how some or logic spammed the db..

A new language isn't going to fix this.... And a team that writes this sort of shit logic clearly shows they are incapable of learning a new one probably...

They are already script kiddies... Don't need them to become babies...

Below is a transcript from work Slack today. Only the names and some code are changed. It ended up causing a bit of drama. DevRanters, what do you take from this?

---

Delivery Lead:
Hey Gang. What's the blocker for FEATURE-123?

Dev1:
FEATURE-122 crashed on iOS app when viewing Feature Introduction page.

Teach Lead:
I've talked about this with Dev1 on a side channel.
And diagnosed the stack trace.
It looks like there is/was some bad handling of a List in the Feature Introduction view logic.
But this is confined to changes that Dev2 is still working on.
(It's not present in master)
Dev2, what's your current position on this?

Dev2:
I have tested at my end with Dev1 but it seems to be working fine

Tech Lead:
There is a race condition related to the use of someList.first()
My guess is that theres a Flow of those lists defined, with an initial value of emptyList
And that on your machine, that Flow is updating with a new value quickly enough that it doesn't matter.
But on Dev1's, for whatever reason, it doesn't get there in time, hits the empty list and falls over.
The logic that's performing the first() needs to gracefully handle empty lists as well.

Dev2:
Where is that logic called?

Tech Lead:
Here's the stack trace Dev1 provided in our conversation earlier:
Caused by: kotlin.NoSuchElementException: List is empty.
...
at 3 iosApp 0x00000000 kfun:kotlin.NoSuchElementException#<init>(kotlin.String?){} + 00
at 4 iosApp 0x0000000 kfun:kotlin.collections#first@kotlin.collections.List<0:0>(){0§<kotlin.Any?>}0:0 + 000
...
at 9 iosApp 0x0000000 kfun:kotlin.coroutines.native.internal.BaseContinuationImpl#resumeWith(kotlin.Result<kotlin.Any?>){} + 0000

This line:
kfun:kotlin.collections#first@kotlin.collections.List<0:0>()
...says that it's first() being called on an empty list.

Dev1:
FYI: Dev3/Dev4/myself are seeing the same issue with the same stack-trace above.

Tech Lead:
So Dev2, have you introduced such a call?
Because I checked master branch and there isn't one, in that version of the file.
Ok, I'll check your working branch Dev2
...
Yes you have here:
var processed1 = someList.first()
var processed2 = someList.first()
...
Lines 123, 124.
Solution looks really straightforward guys.

Dev2:
Okay, I will fix that and push the change

Tech Lead:
Check if someList is empty and allow for generating / handling null processedValues in the view.

Now; I'm going to be straight with you here.
This issue has been discussed over several hours today.
I expect that either one of you could have gone through the process I did in the last 10 minutes above, and resolved it in the same way :point_up:

Dev2:
I went on a break and it's not reproducible on my machine

Tech Lead:
I didn't reproduce it on mine either.

Dev1:
Dev2 and myself are now on sharing screen to sort this issue out. Hope to update back later.

Tech Lead:
<Screen shot of diff with changed code>
:point_up: That change should do it.

Dev2:
Already have pushed the change.

Tech Lead:
...just seen it, is good - same approach :ok_hand:
Dev1 please let us know when tested on your machine.

Dev1:
That does it. It fixes the issues. Thank you, Dev2. I will pick it off from here.

Tech Lead:
Glad to hear it guys.

Dev1:
I have to say this that it is not because we are not working on the issue - Dev2 and myself (together with Dev3/Dev4) have been on this issue all this morning. It just difficult to connect the dot when it wasn't reproducable on Dev2's machine. I brought the issue up because I wanted to switch to working on other tickets while waiting for this to resolve. Still thank you largely for Dev2's work and your keen eyes that spot and resolve the issue quickly.

Tech Lead:
Noted Dev1.
I think the take-away has to be to read the stack-trace carefully... don't worry - we've all been guilty of not reading the error in full, at some point.
The stack trace said that the 'first' element is being referenced from an empty list - that's just logically impossible, right?
Looking for that call to first, we saw it wasn't in the code before, and is after (two of them, in fact).
So then we ask ourselves, how can we deal with an empty list - and then solution almost presents itself.
It didn't really take reproduction of the error to resolve.
Maybe working with a new tech stack creates an anxiety that every issue faced will have a complex solution related to that stack; but I think you'll agree, this particular issue really just required a deep breath and your trusty 'debugging skills 101'... don't lose them! :smiling_face:

Probably the autosave feature in our medical eForm application. You might think that doesnt sound unnecessary, but it was built to solve a problem that shouldnt have existed in the first place.
Autosave was put in place to rescue as much data as possible in the event that the app randomly crashed while a paramedic was filling in a form.
So in one sense it was a necessary feature because the app was so unstable. But on the other hand, if the app was built properly it would never have been needed.

just finished after a full day's work, headed to a bar. their menu is not on paper but an ipad app and it crashed the very second I selected "drinks".

CoWorker: so when are you going to be out?
Me: taking 1 week off Oct 1. I need a break from production issues and all these critical tasks...
CW: ah OK yea, you deserve it. So where you going?
Me: well I'm planning to just stay home unless the weather is really nice. I'm going to try React Native to build a mobile app and maybe look for some open source projects... O yes gotta look into my investments too...

CW: Oohhhh... Ok.... (We go on talking about Trump and why somehow the markets haven't crashed yet...)

FUCK!!! I JUST FINISHED WRITING THE MOST AWESOME RANT BUT THE APP CRASHED RIGHT WHEN I WAS ABOUT TO POST....

TLDR: I wrote an old app and now need it again and amazingly it works...

This pic is now not so effective anymore but that was how I was feeling when I was writing the original

I was almost done with my app and I thought of including 1 extra feature I liked ...and BAMMM app crashed!! can't figure out the bug .. 😵😵
Damn my fucking greed 😫😫

A couple hours ago the devRant's app crashed. Can I rant about devRant on devRant?

Oh the irony! Was checking my app’s crashes on fabric.io iOS app....

And you know what.. Fabric crashed! 🤣 😄 😄

I thought the Devrant app crash problem was fixed? Three times this morning I went to reply to a rant and then the app crashed. Can no longer find the rants and my brilliant contributions remain unrealized. ;)

So I decided to challenge myself as an Android newbie by competing at an hackathon held in my school, which ran for 3 hours.

That's how when I decided to test run the app during the hackathon, the app always crashed upon launching it. Spent some time trying to debug it but I couldn't just resolve the issue at that point(Its currently on my To-do list).

I now decided to start a new project all over again, after about 1 hour had gone 😑.

So yeah that's my first rant. I'm expecting more 😂.

QA guy: Your app crashed on this Samsung.
Me: Checks Firebse logs and finds out that phone was rooted and tells QA guy.
QA guy: You must consider all use cases.

Fuck you dude!

Created a piece of code (code A). It didn't work.
Found a replacement on StackOverflow (code B), commented out my code A and tried the new one.
Everything seemed fine, deleted code A. Tried the app and it crashed.
Re-added the commented code, and the app started working again.

-_____________________-

We had this teacher in uni that was teaching several lectures and one of them being mobile computing ( actual name, but it was just android dev).

So on the first lecture he started to add a single button on the screen and trying to add an onClick functionality. But once he started to write the code he got errors (didn't include Button) and said to everyone:
"Ok, this is normal and now when I click on IDEs save button this will go away" ofc it didn't go aways.

So after 5 minutes of trying to write the full code from head he just opened another project and copied the code he need and tried to run the app (it crashed).

So after about 2/3 of a lecture I stopped laughing and went over to his desk and just hit alt+enter to import the lib and built the project without errors :D

Never went back to those lectures but I passed the class with highest grade by just demonstrating an app I built for fun without any proof that it is actually mine.

More and more, I am getting frustrated/depressed from the attitude of our customers who complain, moan and get angry about issues in their infrastructure, while at the same time, refusing to pay more so the issues could be mitigated.

Like, a client's angry with us today for having one of their non-production-critical databases inaccessible for... Hmm... About 8 hours now (So a whole workday).

Like... I get it, some of your employees couldn't work with it offline, but like... What the hell do we do? You keep data from as far back as several years ago in there, without partitioning, without exports, in a mix of innodb and myisam, so when the DB crashes, and its replication has to be reset from zero, reimporting all the data takes hours upon hours, and importing .sql files just takes time.

Or another client who got angry when their app fell out of the internet, cuz one of their myisam-based log tables crashed, and had to be repaired, with data spanning several years back, meaning it took hours to fix...

The more I work with these "basic" and "simple" infrastructure designs that is *not* redundant, or HA, the more I wonder -- How do the big names out there do it? How do you design systems with fault tolerance so a single DB table crash doesn't lead to the whole app getting inaccessible?

We have... One, exactly one, client, who uses MariaDB with Gallera, and that cluster is *amazing*, it just keeps chugging along, without a care in the world. But it cost them quite a lot, as they had to buy 3 DB servers, instead of 1...

Most fun I had coding?

I was developing my first android app and the database accounted for all the weekdays.

It was a night and I was coding. I build the app after 90 minutes of last build. I was fucking amazed to see that my app was running perfectly on Genymotion Emulator whilst the same god damn build crashed on my phone.

As a new novice developer, I thought it could be due to the OS version difference b/w my phone and VB.

I went on to spent an hour or so, to figure out where I had gone wrong. I re-read my code multiple times and nothing. I could not find a single error in the code.

I was fucking speachless when it hit me, FUCK, today is Saturday (last build was around 11PM Friday) and VM's time is usually screwed (it was Wednesday there) and since I had not accounted for weedends entry in database, the app crashed.

It was really fun having this sort of a bug for the first time in my life. Solved it within minutes after that.

Was reading a very interesting rant, and then devRant crashed 🤨
(Am I supposed to post rants here?)

Jesus on a flaming dragon mobile.

Devrant has so many issues.

The one that was reported the other day where the app crashes on iOS. It crashed four times just now trying to just open it. I proceeded to keep opening and then managed to go to the notifications tab. Crashed again. Click on somethin in the tab. Crashed again. What’s happening here?

Today seems more severe than the odd crashes now and then.

Anyone else using DevRant on iOS 16.0?

It crashes about 1-3 times a day. I haven’t been able to intentionally reproduce. The app just closes.
This never happened in previous versions.

I’m not an iOS dev so not sure how I can help prepare for public release. I’m not even sure if it is the OS, but since it worked with last iOS, I’m guessing.

Some of the events when it crashed.
1. Browsing comments on someone’s post
2. Double tapping to like a comment (it might be the rant as well, I don’t exactly remember)
3. Opening a rant from the list of rants.

Cannot reproduce. For example, relaunching the app and opening the same rant again didn’t cause a crash.

I was working on Figma for more than 6 hours offline and when it was time to save my work with internet, app crashed...

I immediately began to ponder if tech is really worth it 🤣🤣

DevRant Rant. Was commenting on a rant, then the app crashed. Haven't been able to find that rant since. Also, when creating new rant, I still have the text of my last rant here along with tags. On IOS 12.1

Ok so that's my plan, find a kernel with HUGE amout of drivers and , high version.

I built a small os based on linux
-- kernel version 5.0.2 from Plop Linux,
many libraries added 'by hand' -- packages from apts of Debian&Ubuntu, and unpacked packages into system with ArchiveManager,
has GUI but it's called xfree86 ( looks strange when a very old app running on Kernel5 )
So, without compiling, i can make a os.

But i found that Plop didn't compile rtl8188eu module which makes linux support some specific network cards.

I have no professional compiler but a tiny C/Cpp compiler called TinyCC (aka. tcc), but for my pc ( CPU freq = 800MHz ), it seems not possible to compile the module by myself.

And then i downloaded a 5.2 kernel with modules from kernel.ubuntu.com, but when i tried to mount my disk ( part. vfat ), i got some errors like IO charset not found, and then i replaced it with Xanmod kernel but also reported an error said Invalid Arguments, but i checked /proc/filesystems, it supports.

So what can i do? Are there any pre-compiled kernel & modules with 'full common supports'?

I tried kernel 4.4 ( from Ubuntu 16.04 LTS ) just now but the driver crashed when wpa_supplicant tried to initialize the device.