This message was deleted.
# community-supports
Slackbot
04/17/2023, 1:50 PMThis message was deleted.
c
Chris Lee
04/17/2023, 1:52 PMhow is the test getting the resource?
j
Javi
04/17/2023, 1:55 PMI think the problem is related to KMP, I moved everything from
jvmAndAndroidjvmresources Copy code
Thread.currentThread().contextClassLoader.getResource(name)?.file?.let(::File)c
Chris Lee
04/17/2023, 1:56 PMits also possible that resources don’t have a file representation if they are packaged in a jar
j
Javi
04/17/2023, 1:56 PMyou mean the android part more than the
jvmAndAndroidJavi
04/17/2023, 1:56 PMI can try to copy and paste it to android target
c
Chris Lee
04/17/2023, 1:57 PMany use of resources from the classpath - there’s no guarantee of a backing file. cleanest to process those using the inputstream.
j
Javi
04/17/2023, 1:57 PMyeap, it is the android one which is causing the issue
Javi
04/17/2023, 1:58 PMusing inputstream would work on android too?
c
Chris Lee
04/17/2023, 1:58 PMyes
j
Javi
04/17/2023, 1:58 PMwell, technically that would mean coping the file to a different place
Javi
04/17/2023, 1:59 PMI think for my use case it has no sense to get this functionality on Android, thank you, I TIL 🙂
👍 1
e
ephemient
04/17/2023, 7:46 PMresources do exist on Android, but you never have any guarantee that they're backed by
Fileephemient
04/17/2023, 7:48 PMalso even though they work, you should use Android's built-in assets instead of resources, as the former are packaged in a way that allows them to be read efficiently from the APK, while the latter cause https://blog.danlew.net/2013/08/20/joda_time_s_memory_issue_in_android/
👍 2
thank you 1
20 Views