Mobilepay now needs Google Play Services

Made more tests.

Looks like Microg integration issue.

Device attestation is failing. If turning it off feom microG settongs: Login failed.

If on: Something went rong.

If testing device attestation from microG sittengs. it fails.

1 Like

Now on 5.0.0.77

Just paid for a ResQ Club order from Caffitella DUO minutes ago - hopefully I get some karjalanpiirakka and not just a week’s supply of baguettes.

Just tried downgrading to that release and it still just says “something went wrong”. Oh well, fortunately it hasn’t kicked me off MobilePay on my C2 yet so I can still use that. :melting_face:

I get the same thing.
There is an update on microg F-Droid repo, but it is built using different key.
Who built the version we have? Jolla?

1 Like

I tried both the current and old version on the C2. After the succesful identity check (I tried both Mobiilivarmenne and Nordea Id) I got the “something went wrong”, too. Updating MicroG didn’t help.

Mobile Pay isn’t a must-have app for me anymore (before Vipps came along I used it a lot), so I could risk losing it by unregistering on the XA2 (after making a backup), trying the C2 and back to the XA2. Frankensteining old and new settings probably won’t work, though - there’s bound to be a combination of device and personal information.

1 Like

The bundled version is 0.3.15.250932 from the end of April, which is also still the latest version on their github. We bundle their apk and preserve their signature, so installing their new versions to update should be possible. I’ll be able to test that again when there is one.

I don’t think SafetyNet is a thing anymore: https://developer.android.com/privacy-and-security/safetynet/deprecation-timeline

3 Likes

Be sure to not touch the installation on the old phone then! I managed to lock myself out from the old and the new phone.

I didn’t remember to remove the installation from the old phone before installing it to the new one. Then, the new phone’s app “nagged” me to remove it from the old phone. Suddenly, old phone required updating the app, and now I’m too in the “Something Went Wrong” limbo with both phones. :stuck_out_tongue:

1 Like

I reached out to MobilePay via chat. A blunt answer when asking for help for the pin issue was that “Jolla’s phone is not supported, please come back when you have either an Android or an iOS device at use.” So. Since I don’t really need the app, I’ll vote with my wallet and ditch it.

7 Likes

On Xperia 10 III running 5.1.0.11 I have microG version 0.3.11.250932 , how would I get the latest version?

It’s droid-ify that complains on different signatures, they say this is from microG F-Droid repo.

The Jolla-packed-version will arrive with SfOS 5.2. So you have to wait a little bit.

You can send email to support@mobilepay.fi. Remember to highlight European service, putting users to unequal positions for using European services. And that you aren’t demanding native app right now, but them to not be lazy with app development. Every other Finnish bank have made secure app without marrying Google, they could also do it if they wish.

Ask them to forward the request to app dev team.

6 Likes

I’m at this stage now myself as well :frowning:

4 Likes

In the old Xperia III phone I can update mobilepay but it does not accept my PIN. In the new Jolla Phone I can install it and it starts from the beginning, ending up of not accepting a newly created PIN, or the old one. So waiting while they sort out the thing, living without mobilepay should be possible… Using aurora shop tied with google or anonymous to install. In mobilepay they advised to install Chrome and make it default, did not help anyway. Their chat robot ended up in suggesting to contact customer service in office hours.

2 Likes

I had the same problem with the latest update to MobilePay’s sister app Vipps.

The newest version that works on my C2 is 10.16.0 (4429694)

The newest version I able to log in on was 10.20.2 but it was not possible to continue without updating

5 Likes

For me this version works also.

1 Like

Maybe try uninstalling it first.

1 Like

I did. Removed the old one, reinstalled with newest one. No idea why I had a version with different signature..

Had to reinstall most of my android apps for them to “detect play services”.
Sadly Vipps still does not work unless I downgrade to 10.16.0 (4429694). Hope I can use this version for a while now.

4 Likes

Same version works with Mobilepay.

3 Likes

I alao confirm this version works!

Maybe it’s in the thread, but was it only auth that’s broken or can this be safely updated?

1 Like

same here. That version of mobilepay activates with crome browser. Didnt work with duckduckgo for some reason. Using jolla 2 phone.