Arcore-android-sdk: P20 Pro not recognizing surfaces

[Kinghoff]

I'm using a Huawei P20 Pro and it's not recognizing any surfaces. I've downloaded the AR Core App from the Play Store and built the example scene in multiple Unity versions. Other apps like the Porsche Mission E Demo don't work either.
Is there some kind of workaround or fix in the making? Please let me know soon :)

[inio]

Could you provide your build fingerprint? adb shell getprop ro.build.fingerprint should print it.

[Kinghoff]

This is the output of the command:
HUAWEI/CLT-L09/HWCLT:8.1.0/HUAWEICLT-L09/156(C432):user/release-keys

Also it seems to use the middle camera of the P20 Pro with a very low resolution, instead of the upper camera, which appears to be the main one.

[Thoeme77]

Same problem with the P20 Pro and Unreal Engine 4 binary build (v.4.20.3). Other apps which also don't work are ARuler and IKEA Place. The AR origin is constantly moving/drifting and therefore every AR object as well. I've already tried to use several different versions of AR Core back to v.1.2.180425134, instead of the most recent version in the Google Play Store (v.1.5.180910056). Also the planes don't get detected at all or they are drifting as well.

[joensaar]

I can also confirm that AR Core is working very poorly on Huawei P20 Pro (CLT-L29 8.1.0.156(C432patch02)). I have tried updating Unity and Android SDK tools, even Unity 2018.3 Beta. Tried AR Core 1.4 and most recent 1.5x. Ikea app doesn't work either, but the Measure app does work.

[inio]

@AJoensuu thanks for the report. It's odd that Measure works but Hello AR Java doesn't, as they use exactly the same API.

[joensaar]

@inio It is odd indeed. I did some more tests with just the HelloAR example and it seems that it actually works correctly when launching the app for the first time. After closing the app and re-opening, the (rare) planes it manages to find float all over. It does take pretty steady hands to make even that happen. I discovered that clearing the app cache fixes the issue, but it requires that I do that every time.

[inio]

@AJoensuu Thanks for the additional info, this is very helpful.

Does quitting the HelloAR app fix it if you return to it? (open task switcher, swipe HelloAR panel to either side of the screen).

[joensaar]

@inio Nope quitting does not fix it.

[inio]

@AJoensuu: Just to be clear, is it clearing cache for the app (HelloAR Java) or ARCore itself that fixes the issue?

[joensaar]

@inio Actually I should take back what I said about the cache - I cleared the HelloAR cache. It seems to make a difference, but I can't say with certainty, especially because it didn't help much with Ikea Place. Sometimes it works, sometimes not. This is really confusing. The drifting feels like the camera parameters are off or something, causing incorrect depth calculations since sometimes it generates planes on top of each other.

[inio]

@AJoensuu Most likely what's going on is that something about the device state is causing the timestamps on either camera images or IMU data to be inconsistent with the behavior we saw when calibrating the device.

[joensaar]

@inio That sounds very logical. If thats true, that would point to a P20 Pro software update because rolling back to AR Core 1.4x (Play store app) didn't help? I did recently perform an update to my phone. The tracking behaviour is so unpredictable, that it must has fooled me that clearing the cache helped. Sometimes everything works great, sometimes not at all.

[inio]

@AJoensuu Just for thoroughness, what is your build fingerprint? You can get this by running adb shell getprop ro.build.fingerprint.

[joensaar]

@inio HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/156(C432):user/release-keys

[pkettu]

I have the same problem with 'Our World' games AR mode.

adb shell getprop ro.build.fingerprint output:
HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/156(C432):user/release-keys

[inio]

@pkettu Do you only see this in Our World or do you see it in all ARCore apps?

[karlsad]

I have the same issue, however by turning the Master AI in the camera settings on and off sometimes fix the issue. I have no idea why.

[inio]

Good news: we've been able to reproduce this issue and are investigating. Thank you everyone for the reports.

[mrTag]

I have the same problem and was trying out lots of things to get a workaround so that I can continue developing. I think I finally found something that works for me!
For me, the tracking works reliably when I connect my P20 pro to a power source (can be a power bank) before starting an arcore app. But only when I don't use version 1.5 of arcore (I installed the apk of version 1.4.1 and disabled updates in the Play Store).
I messed around with the huawei power saving settings in the beginning and that seemed to help, but it wasn't really reliable. But the whole issue seems to be connected to some power saving tech somehow?

My fingerprint, for what it's worth: HUAWEI/CLT-L09/HWCLT:8.1.0/HUAWEICLT-L09/156(C432):user/release-keys

[inio]

@mrTag THANK YOU!!! You just saved us a lot of debugging work by noticing that.

[jqjq77]

Any good news for this issue ??? my p20 Pro is very hard to find a surface too :<

[inio]

A recent OS update for the Huawei P20 device family has resulted in some devices experiencing poor motion tracking performance. To minimize bad user experiences, we have temporarily disabled access to ARCore and AR-Required apps on the affected devices.

We are evaluating a workaround for this issue in ARCore V1.6, which should be released in the coming weeks. We hope to re-enable all affected devices at that time.

[shugosmail]

I've found a new ARCore version on apkmirror. I tried it and now everything works again! Could you, please, re-enable compatibility for P20 Pro in Google Play? Thank you very much.

[joensaar]

Thank for letting us know @shugosmail !! I've had to explain to clients that ARcore doesn't work on my brand new phone-didn't look good when they asked for me to demo. Thank you ARcore team for fixing this!

[inio]

Today's release of ARCore 1.6 should resolve this issue. Please let us know if it does not.

[inio]

Correction: Access to ARCore has not yet been restored for all P20 devices, so you may be unable to get the update. Over the next few days we will re-enable P20 devices and you should receive the update.

[Kinghoff]

I just downloaded the ARCore 1.6 APK and everything works fine.
Thank you!

[Thoeme77]

I can also confirm that everything is back to normal. I've also used the one from apkmirror since it wasn't unlocked in my region yet.

[inio]

@Thoeme77 There's no need to go to third-party sites to get the APK, we provide them on our releases page.

[Thoeme77]

@Thoeme77 There's no need to go to third-party sites to get the APK, we provide them on our releases page.

Oh thanks!

[antonGritsenko]

@inio sorry for asking, but do you know any dates when it will be globally available? Sure, I can download APK, but this is not an option in case when you need to use other apps from Google Play, they also blocked at the moment for same reason as ARCore itself.

[calmmycode]

Still does not work on P20 Pro (CLT-L29) with ARCore apk v1.6 from releases section. @inio

[NGrigorov]

I hope @inio you guys manage to solve the P20 problem quickly! ARcore not working for P20 is a really big issue for the people in my position :D we are having to work with version 1.1 and the track is so bad because of the software update on the P20 family there

[calmmycode]

Same here. We have only pixel gen1 and p20 pro for AR Tests. Very big need in fix for p20 pro. The problem exists on CLT-L29 (C636) with firmware 8.1.0.155 (Android 8.1).

[joensaar]

@calmmycode C636 is one of the region codes for the Asian market. It could be that you have a software update available that will make it work. If not, you may have to wait for Huawei to release an update. I'm currently running 8.1.0.161 (C432) = European region.

[calmmycode]

@AJoensuu @inio after update android pie - build 9.0.0.168(C636) - still does not work

[calmmycode]

Any news? ARCore does not work on 8.1.0.155, 8.1.0.158, 9.0.0.168. What we need to do to make it work?

[inio]

@calmmycode

1. What is the build fingerprint of your device? adb shell getprop ro.build.fingerprint should display it.
2. Is ARCore available for your device from the Play Store (non-China) or Huawei AppGallery (China)?
3. Just to confirm, the session starts but you never detect any planes?

[nathanb3]

@inio I am also experiencing ARcore not working on Huawei P20 Pro. 9.0.0.160

1. HUAWEI/CLT-L04/HWCLT:9/HUAWEICLT-L04/160C792R1:user/release-keys

2. ARCore downloaded from play store. Version 1.6.181112096

3. I try to open the Measure app and it just pops up saysing : Unknown ARcore error (Unavailable-DeviceNotCompatibleException).

[calmmycode]

Hi, @inio Here is some info:

1. HUAWEI/CLT-L29/HWCLT:9/HUAWEICLT-L29/168C636R1:user/release-keys
2. Device has all Google Services, but ARCore is not availiable from Google Play. If I instal ARCore manually from downloads section on github, I get error "This device does not support AR"
3. The session can not start. No camera view. Only black screen and error "This device does not support AR"

[maguileracanon]

Hi @inio
As issue #641 was closed. May I ask for advice from the community. I need to choose a device to do research with Google Arcore in China. I was thinking about Huawei as it has more international support and I have no experience with Xiaomi, but after seeing all of the issues I was wondering which devices are more stable in China to develop ARcore apps. Could you please recommend me one? or do you maybe know who can I approach for some advice on this?

[calmmycode]

Much time passed, pls, keep us updated about any info about the issue @inio

[NTrixner]

This doesn't seem to be happening anymore with my P20 Pro, i.e. ARCore seems to work fine again.

[calmmycode]

Hi. Pls, any news on this issue @inio

[mandanakhademi]

it doesn't work on Huawei P20 pro, CLT-L29
Build 9.0.0.159. ARCore version was 1.6181112096.
I've tried to use Google measurement app but it displayed unknown arcore error (Unavailable-DeviceNotCompatibleException)

[diogoalexsmachado]

I'm still having this issue... ARCore 1.6 installed and can't use any AR apps under the message "Device not supported"

[ilias-uoc]

I'm having this issue as well. My phone recently got the Android Pie update and I was hoping the update would fix this but it didn't :( I can download ARCore from Google Play but when I use Google Measure I get the Device not compatible exception. My phone's model is CLT-L29.
Has ARCore ever worked for this phone?

[Degar00]

Hi all! I´m currently having the same issue described just up here. I can provide any data you want from my cell if it helps solving it.

My cell:
model is CLT-L29
compilation: 9.0.0.195(C43 2E5R1P9) GPU TURBO
Ar Core version 1.7.190128066

If you need some log or anything just ask for it.
Thx!!

[calmmycode]

Tired of waiting when we get the fix. 1 year passed after this phone was released.

[SalvatoreMeschini]

Same issue here with

Model: CLT-L29 (Huawei P20 Pro)
Build number: 9.0.0.195 (C432E5R1P9) GPU TURBO
Ar Core: 1.7.190128066

Google Measure shows "Unknown ARCore Error (Unavailable DeviceNotCompatibleException) and AR Ruler shows something like "Failed to create AR session".

I also tried to delete ARcore data/cache but it did not help

[Wierka85]

Model: CLT-L29 (Huawei P20 Pro)
Gra: Pokemon Go, jak włączam AR+ to aplikacja się zawiesza. Nie działa nic co ma tryb rozszerzonej rzeczywistości nie działa. Niby wspieracie ten model a to kłamstwo. Pokazuje się czarna kamera. Jak czytam i słyszę większość ma ten sam problem.

[Wandrer]

I'm one of these people where it works
and then there is someone in one of my communities where it doesn't.

I'm on Android 9.0.0.195 C432
as this person too.

I'm using a Vodafone firmware 9.0.0.5(CT.F01) if this helps. I also did disable Google Instant Play the moment it was released. I'm using the SingleSIM version CLT-L09C432.
ARCORE works at least in Pokémon GO, Our World and Google Measure, those i tried before.
Is there a way to find out or to send diagnostics data, to find out why some devices work and others don't?

[Raerion]

On my brand new P20 Pro ARCore does not work, too. Strange that it works for some people.

I’m using the Dual SIM Version CLT-L29 with Build 9.0.0.195(C432E5R1P9) with a provider package from Telekom Germany DT.DEU 9.0.0.5(CT.F01).
ARCore was actually included in the update to EMUI 9 and was updated via PlayStore to 1.7.190128066.

Tested apps: Google Measure throws an “Unknown ARCore error (Unavailable-DeviceNotCompatibleException)”, Grymala AR Plan 3D quits with “This device does not support AR” and Niantic Pokemon Go just crashes with a black screen.

@inio Could you please provide a status update? Is this issue still under investigation?
Since the error messages indicate compatibility errors - is it possible that not every possible P20 Pro device/firmware version has been enabled or re-enabled after the temporarily disabled access in Nov 18?

[Wandrer]

Could it be that L09 the SingleSIM does work and L29 the DualSIM not?

Maybe only the SingleSIM was added to the compatibility list or DB, but not the other device versions.
At least for the black screen issue.

[SalvatoreMeschini]

Could it be that L09 the SingleSIM does work and L29 the DualSIM not?

Maybe only the SingleSIM was added to the compatibility list or DB, but not the other device versions.
At least for the black screen issue.

It might be... I confirm that on my:

Model: CLT-L29 (Huawei P20 Pro)
Build number: 9.0.0.195 (C432E5R1P9) GPU TURBO
AR Core: 1.7.190128066

does NOT work:

• Google Measure shows "_Unknown ARCore Error (Unavailable DeviceNotCompatibleException)_"
• AR Ruler shows something like "_Failed to create AR session_".

The device is DUAL SIM.

[joensaar]

@SalvatoreMeschini I have the EXACT same configuration. Works normally.

[SalvatoreMeschini]

@SalvatoreMeschini I have the EXACT same configuration. Works normally.

Which region? Not sure if that's relevant, but it looks like all the other users with CLT-L29 are less lucky.

[joensaar]

@SalvatoreMeschini It's CLT-L29 C432.

[diogoalexsmachado]

@SalvatoreMeschini It's CLT-L29 C432.

same as mine

[karlsad]

My p20 pro seem to be working correctly, I use the newest available version
of ARcore. My phone: CLT-L29, Version 9.0.0.163(C432E5R1P9) Android version
9

Den mån 25 feb. 2019 kl 13:48 skrev Diogo Machado <[email protected]

:

@SalvatoreMeschini https://github.com/SalvatoreMeschini It's CLT-L29
C432.

same as mine

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/arcore-android-sdk/issues/585#issuecomment-466998801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApCiCzXzYljntpqpFXVbpkE0OBiMBqUKks5vQ9uUgaJpZM4W-fdy
.

[ilias-uoc]

My p20 pro seem to be working correctly, I use the newest available version of ARcore. My phone: CLT-L29, Version 9.0.0.163(C432E5R1P9) Android version 9 Den mån 25 feb. 2019 kl 13:48 skrev Diogo Machado <[email protected]
…
: @SalvatoreMeschini https://github.com/SalvatoreMeschini It's CLT-L29 C432. same as mine — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#585 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/ApCiCzXzYljntpqpFXVbpkE0OBiMBqUKks5vQ9uUgaJpZM4W-fdy .

Maybe that's the issue. It does not work for the CLT-L29, version 9.0.0.195(C432E5R1P9) phones.

[nathanb3]

Not working on CLT-L04 9.0.0.178.

[diogoalexsmachado]

just updated to 9.0.0.195(C432E5R1P9) on my P20 Pro (CLT-L29) and it is still not working.

[Wandrer]

@diogoalexsmachado: Could you reset the ARCORE app cache?

[diogoalexsmachado]

@diogoalexsmachado: Could you reset the ARCORE app cache?

Yes I did. I even downgraded and re-updated the app from Play Store

[karlsad]

Working fine on my P20 Pro, same update as you. Very strange...

http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virusfritt.
www.avg.com
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Den tis 26 feb. 2019 kl 13:21 skrev Diogo Machado <[email protected]

:

just updated to 9.0.0.195(C432E5R1P9) on my P20 Pro (CLT-L29) and it is
still not working.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/arcore-android-sdk/issues/585#issuecomment-467417516,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApCiC-m5DOji-djr0es_v9OyA2l_a2Tnks5vRSa5gaJpZM4W-fdy
.

[SalvatoreMeschini]

Working fine on my P20 Pro, same update as you. Very strange...

Could you please go to Settings -->System --> Phone info (first entry) and provide here the following information:

• Model
• Build number

?

[karlsad]

Model - CLT-L29

Version - 9.0.0.195(C432E5R1P9)

Got android version 9

http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virusfritt.
www.avg.com
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Den tors 28 feb. 2019 kl 10:05 skrev Salvatore Meschini <
[email protected]>:

Working fine on my P20 Pro, same update as you. Very strange...

Could you please go to Settings -->System --> Phone info (first entry) and
provide here the following information:

• Model
• Build number

?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/arcore-android-sdk/issues/585#issuecomment-468193738,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApCiC56cSsSLloxfmaBPDq2lN_p7gQW9ks5vR5vwgaJpZM4W-fdy
.

[SalvatoreMeschini]

This is what I found in my Logcat:

02-28 11:56:07.393 I/native (19540): device_profile_database_helpers.cc:419 Found nothing for UUpC5W
02-28 11:56:07.393 I/native (19540): device_profile_database_helpers.cc:419 Found nothing for CLT-L29/HWCLT_accelerometer-lsm6dsm_OFILM
02-28 11:56:07.393 I/native (19540): device_profile_database_helpers.cc:419 Found nothing for J1ASAV
02-28 11:56:07.393 I/native (19540): device_profile_database_helpers.cc:419 Found nothing for HWCLT_accelerometer-lsm6dsm_OFILM
02-28 11:56:07.393 I/native (19540): device_profile_database_helpers.cc:419 Found nothing for ioG7OZ
02-28 11:56:07.393 I/native (19540): device_profile_database_helpers.cc:419 Found nothing for CLT-L29
02-28 11:56:07.393 I/native (19540): device_profile_database_helpers.cc:421 Could not locate device profile for HUAWEI/CLT-L29/HWCLT_accelerometer-lsm6dsm_OFILM:9/HUAWEICLT-L29/195C432R1:user/release-keys
02-28 11:56:07.393 E/native (19540): calibration_jni.cc:184 No device profile available for build fingerprint HUAWEI/CLT-L29/HWCLT_accelerometer-lsm6dsm_OFILM:9/HUAWEICLT-L29/195C432R1:user/release-keys
02-28 11:56:07.395 E/native (19487): session_create_implementation_shared.cc:870 Unable to obtain device profile from the content provider: generic::not_found: Device is not supported.
02-28 11:56:07.395 E/native (19487): session_create_implementation.cc:108 Failed to create calibration provider.
02-28 11:56:07.395 W/native (19487): session_create_implementation.cc:109 ArSession_createWithSettingsImplementation_private returning ArStatusErrorSpace::AR_UNAVAILABLE_DEVICE_NOT_COMPATIBLE: .

[rgm00003]

Hello.
I have a p20 pro CLT-L09, latest compilation number 9.0.0.210 and I have the problem, AR not working.

[Raerion]

Just received an update for ARCore (1.7.190128146). It doesn't fix this issue, device is still registered as incompatible.

[SalvatoreMeschini]

The device build fingerprint is:
HUAWEI/CLT-L29/HWCLT:9/HUAWEICLT-L29/195C432R1:user/release-keys

But in the logcat I found the following entry:

No device profile available for _build fingerprint_ HUAWEI/CLT-L29/HWCLT_accelerometer-lsm6dsm_OFILM:9/HUAWEICLT-L29/195C432R1:user/release-keys

Is this inconsistency causing the AR_UNAVAILABLE_DEVICE_NOT_COMPATIBLE error?

[Maeihra]

Hello.
I've tried to use Google Measure app with my p20pro but it showed the "Unknown ARCore error (Unavailable-DeviceNotCompatibleException)." message. Unhappy with this result I contacted another p20pro user. Measure is working fine on his phone.

The difference between these two phones is the accelerometer/gyroscope sensor.

The working phone uses the lsm6dsm.
My phones uses the icm20690.

[Wandrer]

The friend of mine has the same ICM20690.

It seems it's a whitelisting problem at all, as this sensor is not whitelisted.

Will this require an update or is the compatibility DB an online feature only cached offline?

[nathanb3]

@inio Any update on this? There seems to be a lot of people now with the same issue.

Thanks.

[Raerion]

I can confirm the issue with the ICM20690 accelerometer/gyroscope. My device is also using this sensor.
Thanks @SalvatoreMeschini for pointing this out!

[dementia2029]

Same here. I have ICM20690 accelerometer/gyroscope. @inio Would you kindly tell us any info?

[SalvatoreMeschini]

The difference between these two phones is the accelerometer/gyroscope sensor.
The working phone uses the lsm6dsm.
My phones uses the icm20690.

It is not working on my P20 Pro and accelerometer/gyroscope sensors are both lsm6dsm.

This is what I can see in my logs:
No device profile available for build fingerprint HUAWEI/CLT-L29/HWCLT_accelerometer-lsm6dsm_OFILM:9/HUAWEICLT-L29/195C432R1:user/release-keys

[Wandrer]

Could some dev tell us which P20 Pro versions with which gyros do have a profile?

[dementia2029]

I am so indignant of Google support

[joensaar]

The guys at Mountain View could definitely give some kind of response, but I wouldn't go pointing fingers at them because of this issue. Huawei already made breaking software changes, (the reason this thread was originally made). So then they (probably) changed inertial sensor supplier since P20 family launch, and then expect Google to fix a problem they caused? I'd say this is about money and Huawei's lack of interest. Whats in it for Huawei when P30 family is coming? Nothing. Huawei won't be my next phone.

[SalvatoreMeschini]

Version 1.8.190311076 fixed the compatibility-related issue and my P20 seems to detect surfaces.

[dementia2029]

Same here!

[MohammedAlSafwan]

Version 1.8.190311076 isn't working for me. I tried re-installing it and still the same problem. nothing is being detected.
I had to download the older version 1.7.19012814, it worked perfectly.

[joensaar]

Well, well. I was one of the lucky ones that it was working for. Now it stopped working for me with v1.8.190311076. I guess one's loss is another's gain. Here's my build fingerprint: HUAWEI/CLT-L29/HWCLT : 9/HUAWEICLT-L29/203C432R1 : user/release-keys

[paallysaho]

Same for me as for Mohammed Al-Safwan. Version 1.8.190311076 is not working, but earlier version 1.7.190128146 works perfectly.
My build fingerprint: HUAWEI/CLT-L29/HWCLT:9/HUAWEICLT-L29/203C432R1:user/release-keys

[SalvatoreMeschini]

So it seems that there are (at least) 2 distinct fingerprints for P20 Pro:

• HUAWEI/CLT-L29/HWCLT_accelerometer-lsm6dsm_OFILM:9/HUAWEICLT-L29/195C432R1:user/release-keys
• HUAWEI/CLT-L29/HWCLT:9/HUAWEICLT-L29/203C432R1:user/release-keys

1.8.190311076 is finally working with HUAWEI/CLT-L29/HWCLT_accelerometer-lsm6dsm_OFILM:9/HUAWEICLT-L29/195C432R1:user/release-keys, but now HUAWEI/CLT-L29/HWCLT:9/HUAWEICLT-L29/203C432R1:user/release-keys appears to be no longer supported.

Just wondering: is it possible to add both of them to the list of supported models?

[LukeTheWrapper]

IK don't get any AR Core App working, Uninstalled, reinstalled, Downgraded... Nothing works...

Model - CLT-L29

Version - 9.0.0.195(C432E5R1P9)

Got android version 9

[Schpammer]

My phone isn't detecting surfaces neither.

Fingerprint:
HUAWEI/CTL-L29/HWCTL:9/HUAWEICLT-L29/236C432R1:user/Release-Keys

[danielwikstrom]

My phone isn't detecting surfaces neither.

Fingerprint:
HUAWEI/CTL-L29/HWCTL:9/HUAWEICLT-L29/236C432R1:user/Release-Keys

Same for me. Have the exact same fingerprint:

HUAWEI/CLT-L29/HWCLT:9/HUAWEICLT-L29/236C432R1:user/release-keys

[danielwikstrom]

Just installed v1.9 and its working perfectly! @Schpammer you should try it out aswell, as you have the same fingerprint as me

[paallysaho]

The 1.9.190422056 version (updated on 1.5.) works also for me (build fingerprint: HUAWEI/CLT-L29/HWCLT:9/HUAWEICLT-L29/203C432R1:user/release-keys).

[Schpammer]

1.9 is working. Thanks for that hint!

[devbridie]

As a part of ongoing efforts to maintain ARCore repositories, I’m closing this issue as stale since it hasn’t had activity in more than 6 months. If this issue is still relevant, please feel free to file a new bug using the latest version of the SDK.