I’m seeing some binder TransactionTooLargeException-related crashes on current production which are caused by now obsolete serialization which is still being triggered somewhere
unfortunately, this exception is deep within android guts so the stacktrace is largely useless.
tldr: if current version of app crashes for you (more often than usual) post what you were doing to trigger it.
yeah, most likely
i’m not sure if i want to rewrite everything on their new api tbh, this whole “we broke everything haha deal with it” shtick is getting old at this point
alright so the workaround for the widget didn’t help
i haven’t looked at the jobscheduler yet but the chances of me rewriting anything are slim, at this point i would prefer to eventually remove the widget altogether
currently there’s like 10 people affected by this issue anyway so its not a priority i’m afraid
i’d like to add that while widget should be rewritten one way or another to work on 8.0 (it’s a low priority though because at this point - going by google crash statistics - literally EIGHT people are affected by this issue), tasker support is very likely not going to see any updates.
supporting a specific proprietary app has been a mistake in the first place. i’m not going to remove anything just yet but it should be considered EOL.
the only use for it is related to offline mode which is, as far as i’m concerned, is generaly a deprecated thing in itself ityool 2018.