Yousician App never fully loads on FP6

On a new fp6, bought with e/OS/ (3.0.1 official). The Yousician app installed via the App lounge starts, let’s you log in to your account, but never concludes its boot sequence (black screen with Yousician text and three wiggling bars below).

Any hint / idea appreciated. Yousician works on my Android FP4.

I disabled tracker block to exclude errors stemming from that and reproduced to the splash screen you described.

There’s lots of info debug output, nothing really conclusionary but a few error lines concerning UnityIAP. Probably up to that?

logcat
E Unity   : Yousician.Revenue.Shop.PaymentProviders.UnityIAP.UnityInAppService:OnInitializeFailed(InitializationFailureReason, String)
E Unity   : UnityEngine.Purchasing.Extension.UnityUtil:Update()

microG has a dozen entries on general Unity things, some solved/implemented, some not. UnityIAP (in-app-payments) didn’t come up yet.

Thanks for having checked!

For future reference, I am trying the “Guitar and bass” Yousician app.

version 5.13.0
com.yousician.yousician

I think there’s a separate app for other instruments (piano, …) but I am not sure.

that’s the one I gave the test run. I’m quite sure it’s up to UnityIAP. If you already have a paid account with them you can probably ask if they can change the load order to have a fallback for existing, paid accounts?

FYI, i wrote to their helpdesk (i am a paid suscriber after all). I received a nice reply to tell me that they don’t support nor have plans to support alternative OSs. I still asked them to pass this to their developer team, so who knows maybe one day.

If you are a Yousician developer reading this, thank you for your time, we are rooting for you.

I you are a Yousician user, please consider sending them an email linking to this discussion.

1 Like

And update:

My phone now runs e/OS/ 3.0.4, Yousician 5.15.0. Same same.

unlikely this changes, Yousician is in the business of writing a guitar app, not mobile OS SDKs. You’d need to get a Unity dev deeply caring for microG or the other way round to make it work.

on a tangent..

foss Android “has no SDK” that devs could hook into as they come to expect. Even if the niche becomes big enough, there’s no replacement ecosystem. microG is relaying mostly to Google. So if the IAP in Unity would work, it’s handled via Google Billing API.

What it looks like if SDK compatibility is directly worked out between libraries, this is what Huawei does to make Unity IAP work:

I’d post to microg issues to ask for UnityIAP ↔ Google Billing API compatibility. Unsure how much is needed for that to work. And post to the Unity forum that there are foss Android users with credit cards