I have an app which receives VIEW intents from the file browser. If it receives one from a 'cold' start (ie app has not been started before or has been stopped) then the callback doesn't fire, so it's hard to get the intent. I posted to the kivy-users mailing list. Someone suggested it was a bug. Is it a bug? When the app is starting the callback hasn't been assigned so I'm not sure. In any event it would be more intuitive if it would fire for the first intent.
The code I've used to get the intent on a cold start is:
from jnius import autoclass
PythonActivity = autoclass('org.renpy.android.PythonActivity')
activity = PythonActivity.mActivity
intent = activity.getIntent()
file_uri= intent.getData().toString()
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
I have an app which receives VIEW intents from the file browser. If it receives one from a 'cold' start (ie app has not been started before or has been stopped) then the callback doesn't fire, so it's hard to get the intent. I posted to the kivy-users mailing list. Someone suggested it was a bug. Is it a bug? When the app is starting the callback hasn't been assigned so I'm not sure. In any event it would be more intuitive if it would fire for the first intent.
The code I've used to get the intent on a cold start is:
from jnius import autoclass
PythonActivity = autoclass('org.renpy.android.PythonActivity')
activity = PythonActivity.mActivity
intent = activity.getIntent()
file_uri= intent.getData().toString()
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.