You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the list of instances to upload is exposed through generic VIEW and EDIT actions. This is unexpected and also means that other apps respond to the same action so Collect has to be picked out of a list. It would be useful to add a custom-named action that better describes what the activity does and narrows down the responding applications. See #3045 for additional context.
There already is org.odk.collect.android.INSTANCE_UPLOAD" with MIME type vnd.android.cursor.dir/vnd.odk.instance" for uploading a single instance. I wish we had used org.odk.collect.UPLOAD_INSTANCE instead to better match Android naming conventions but so it goes.
For this new action, we could do something like VIEW_INSTANCE_UPLOAD_LIST or VIEW_UPLOADS. We could use the probably more expected org.odk.collect. namespace or use org.odk.collect.android. to match other custom actions.
The text was updated successfully, but these errors were encountered:
Currently the list of instances to upload is exposed through generic
VIEW
andEDIT
actions. This is unexpected and also means that other apps respond to the same action so Collect has to be picked out of a list. It would be useful to add a custom-named action that better describes what the activity does and narrows down the responding applications. See #3045 for additional context.There already is
org.odk.collect.android.INSTANCE_UPLOAD"
with MIME typevnd.android.cursor.dir/vnd.odk.instance"
for uploading a single instance. I wish we had usedorg.odk.collect.UPLOAD_INSTANCE
instead to better match Android naming conventions but so it goes.For this new action, we could do something like
VIEW_INSTANCE_UPLOAD_LIST
orVIEW_UPLOADS
. We could use the probably more expectedorg.odk.collect.
namespace or useorg.odk.collect.android.
to match other custom actions.The text was updated successfully, but these errors were encountered: