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
{{ message }}
Repository navigation
autoclass: Class only found when called in specific places? #2242
We got the error jnius.jnius.JavaException: Class not found b'com/arthenica/mobileffmpeg/FFprobe'. The fix for it is put ffprobe = autoclass('com.arthenica.mobileffmpeg.FFprobe') in __init__.py but it seems not straightforward to me. I would like to get some thoughts on it.
get_video_length was called on different thread from main thread
All the examples show autoclass calls that are global (and probably more to the point static)
So perhaps it matters when autoclass happens?
The usage shown here is local, moving it to __init__.py would make it global.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have the means to take action. Please reach out if you have or find the answers we need so that we can investigate further.
Activity
[-]Autoclass works unexpectedly[/-][+]autoclass: Class only found when called in specific places?[/+]RobertFlatt commentedon Jun 25, 2020
Hmm, interesting....
All the examples show autoclass calls that are global (and probably more to the point static)
So perhaps it matters when autoclass happens?
The usage shown here is local, moving it to
__init__.pywould make it global.And while digging I found this, which may be also be interesting
https://pyjnius.readthedocs.io/en/stable/api.html#pyjnius-and-threads
praaggg commentedon Jan 9, 2021
In my case the build itself fails while using below in spec file
android.gradle_dependencies = com.arthenica:mobile-ffmpeg-full:4.3.2
dbnicholson commentedon May 31, 2022
I think the issue is most likely that you're trying to resolve the class from a new native thread. See #2533 for details.
Julian-O commentedon Nov 20, 2023
@cathay Was this resolved by the comment above?
github-actions commentedon Jan 1, 2024
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have the means to take action. Please reach out if you have or find the answers we need so that we can investigate further.