I am getting a FlurlHttpException axception whie making first https request in the ASPNZ Xamarin app. Taget mobiel devices is a Samsung S10+ running Android Version 9. (PIE). My minimum taget version is API level 23. The initial GET is to Azure, but throws exception before it even leaves phone, URL : https://????.azurewebsites.net/AbpUserConfiguration/GetAll
short version exception : exception {Flurl.Http.FlurlHttpException: Call failed. Didn't find class "md53445bfa005abb70b0a2fcd6c25bc64be.AwaitableOkHttp_OkTaskCallback" on path: DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file "/data/app/com.????.Mobile-efnJv1yo0JoM5swt4qJ1-g==/base.apk"],nativeLibraryDirectories=[/data/app/com.????.Mobile-efnJv1yo0JoM5swt4qJ1-g==/lib/arm64, /data/app/com.????.Mobile-efnJv1yo0JoM5swt4qJ1-g==/base.apk!/lib/arm64-v8a, /system/lib64]] GET https://????.azurewebsites.net/AbpUserConfiguration/GetAll ---> Java.Lang.ClassNotFoundException: Didn't find class "md53445bfa005abb70b0a2fcd6c25bc64be.AwaitableOkHttp_OkTaskCallback" on path: DexPathList[[zip file "/system/framework/org.apache.http.legacy.boot.jar", zip file
Anynoe have any infight on this excpetion of suggestions appreciated.
9 Answer(s)
-
0
Hello Tom, I've ran into this same issue. I found that it has to do with the visual studio version that is currently installed. When running the app from visual studio 2017 (15.9.12 or 15.9.8 ) I have no issues getting the app to successfully make Http requests through the FlurlHttp pluggin. However, as soon as I try to make the same call that is mentioned in your post on visual studio 2019 (16.1.2) I receive the same error that you have posted. Working from a base project template I'm able to readily reproduce the issue just by trying to debug the app via android emulator or any android device I try to use. Using visual studio 2017 works as a workaround for now, but this does need to be addressed. If support is in need of a sample solution to recreate this issue I can provide one.
-
1
yes, Thanks for the reply. I was able to revert back to 2017 as well and seem to fix the issue. LogCat gave me no further detials to help. I am investigating it further to try other targets, however all droid versions seem to behave the same. Thanks for the reply !
-
1
I also created a sample stand alone Flurl app that behaves in same manner wehn biult from 2019.
-
0
I was curious if this was primarly a flurl issue, and from your investigation it seems that it is. Have you created an issue on the Flurl git hub repo? If you have I would be interested in following it.
-
3
Yes, I still must do this. I want to give them as much information as I can. I manipulated target version and then backed up to XF 3.X , with same result. So, at this point, I am 90% certain it’s a by-product of the S2019 image creation. I will post issue here to allow you to follow. Thanks again
-
1
Hi, I'm getting same issue from a fresh new Xamarin Forms project on VS 2019 with Flurl... no issue when trying with VS 2017 !
-
1
dedicated issue created : https://github.com/tmenier/Flurl/issues/453
-
0
Thanks for creating the issue!
-
0
Thanks @ricavir
