The receiver for GET_NOTE and SEARCH intents seems to return dictionaries with consecutive alphabetic keys instead of descriptive names, when called from Automate

[decadent]

✓ I have searched for existing issues that may be the same as or related to mine.

This is more a question for @NatKarmios regarding the workings of the ExternalAccessReceiver. I'm doing GET_NOTE or SEARCH calls with Automate, and getting the result in a weird format:

{"a":true,"b":{"a":15371,"b":"Note title","c":"","d":[],"e":[],"f":"The Notebook","g":null,"h":null,"i":null,"j":null,"k":null,"l":1539652080000,"m":{"CREATED":"[2018-10-16 Tue 04:08]"}}}

It's the right note, but the field names for both the result and the note are just one-letter in alphabetic order, while the docs specify descriptive names (which I would certainly prefer).

As I understand it, the result data is sent as a string, so I'd expect that Automate doesn't do anything to it. Do the field names originate in the Orgzly receiver like this? Would it be possible to change them to descriptive names?

I'll try to also test in Tasker and with am start if I ever figure out how to do this kind of intents with them. I also looked in the code for a bit, but I'm not an Android programmer, so it's rather thick for me—meanwhile perhaps you already know the answer as to whether it should happen and why it could.

Device: Pixel 3a
Android Version: 12
Orgzly Revived Version: 1.8.19
Repository type(s) used: local files