oSumAtrIX
oSumAtrIX
> My assessment is based on this comment Guess what can change is viewing per patches then. Tapping on view patches for a specific patches file can open the patch...
> Therefore, apparent complexity should not justify a place on that milestone. I have done parts of this issues work already when I created the issue to confirm if it's...
> If you are referring to code consistency then I don't think it justifies being on the milestone either, since refactoring can always be done after merge to main and...
> If you are referring to UI consistency, can you show a specific example and motivate why it is bad and justifies milestone placement? Well I am not sure what...
> This would mean you have to select an app in order to view patches for it. Regardless, big design changes are up to the designers, not you and me....
Uncheck patches until the issue is gone. Report back which one caused it
I don't remember but wasn't there a solution to this? Besides, user above used GmsCore support patch only, but i don't remember if that depends on the spoof client patch
IIRC we had a solution for this issue once by patching one of the requests for updating the history
I dislike band-aid solutions. For a couple of painful days I am experimenting a proper solution such as using a different transformer implementation like Saxon. Hopefully a proper solution can...
I was thinking of a more efficient solution which is to hook the output stream and modify it. This avoids writing to string, modifying it, then writing it to the...