due to some additional retarded decisions from google the beta is going to be prolonged i guess
more info here: https://issuetracker.google.com/issues/37103380#makechanges
also, if you get crashes on 7.1 it’s normal
e: best part how this crash gives you zero information to figure out what the deal is and you have to go google shit until you find out its google silently changing rules for how a very important thing (state saving) works.
From that doc, the 1MB is “is shared by all transactions in progress for the process. Consequently this exception can be thrown when there are many transactions in progress even when most of the individual transactions are of moderate size.”
Which means any call to save instance state can push you over the limit, even if it’s tiny. So, again, how is one supposed to know they’re potentially breaching that limit?
basically “we trained everyone for years to obsessively serialize activity/fragment state on exit because our retarded bespoke platform literally restarts your application when you rotate your phone, which is something we thought was a good idea. well, now we’re making actual storage limits for this serialization protocol we wanted you to use completely unpredictable thus making built-in state saving thing completely useless. no, there’s no alternative provided other than “use the database, lol.” additionally, fuck you.”
Through testing, apparently the WebView.saveState() method adds a byte array of several kilobytes per page in the WebView history stack. The size seems to vary depending on the page content. One link resulted in 8 KB added to the Bundle; 10 links totaled 140 KB; I randomly clicked around a news site for a few minutes, and the byte array seemed to top off around 400 KB. I guess the history stack truncates after a certain length.
fucking lol, i’m retargeting sdk 23.