Expose service to let Element X access some internal data#9109
Expose service to let Element X access some internal data#9109
Conversation
|
|
||
| import android.os.Bundle | ||
|
|
||
| interface DataImporter { |
There was a problem hiding this comment.
Just a thought: would this be better named DataExporter? Then on the EX side it is named "importer"? e.g. the EX importer talks to the EC exporter.
There was a problem hiding this comment.
Yes. This file will be removed in a future version of the code, which just have the ImporterService. Maybe I should name it ExporterService, but since it's used by EX to import a session, I am not sure.
Note: Using permission "${applicationId}.READ_DATA" with android:protectionLevel="normal" does not work in release mode.
e364976 to
2fc12ad
Compare
|
Type of change
Content
Temporary code to let Element X access some internal data.
See element-hq/element-x-android#6013 for more details.
Motivation and context
Part of element-hq/element-meta#3073
Screenshots / GIFs
Tests
Tested devices
Checklist