Ask / Submit
4

Store error [answered]

asked 2016-08-14 13:04:31 +0200

eson gravatar image

updated 2016-08-14 16:28:35 +0200

Am I the only one having problem with Store? I can only see very few apps, maybe 10-15. Most categories are totally empty. "My apps" page also empty.

I did factory reset this morning, and upgraded OS to 2.0.2.48. Sailfish basic apps installed and after that I tried Store to get my favourite apps

App data base rebuild done, with no changes.

Update:
Another factory reset and now Store works as expected. This time on SFOS 2.0.2.43

Update2:
This definitely is a bug. Same thing happened again, directly after 2.0.2.48 upgrade, Store stopped working properly. Same behaviour as abowe.
This time I have working apps installed, because I installed what I needed before OS upgrade.
No Warehouse, no tweaking what so ever. The only thing made was a backup restore, from previous 2.0.2.48 config.

Update3:
And it's working again! I'm far from convinced but I think it was pkcon refresh from terminal that did it.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by eson
close date 2016-08-14 19:21:17.098360

Comments

store is working here with 2...48. maybe a temp store issue?

pawel ( 2016-08-14 14:02:57 +0200 )edit
1

@pawel I had the exact same problem previous reset I did. That makes me pretty sure it's a 2...48 issue.
I have also had more problems with that version, like not being able to create new playlists in stock media player, apps not working with settings transferred from my Jolla 1 and so on. That's why I made a reset in the first place.

eson ( 2016-08-14 14:21:12 +0200 )edit

1 Answer

Sort by » oldest newest most voted
8

answered 2016-08-14 19:13:56 +0200

Keto gravatar image

This is most likely a known issue we have in the store backend. In some rare, and at the moment unknown circumstances it fails to identify the device correctly. In this case it can't show the correct list of installed applications and puts the device in the "unknown" group, thus showing only very limited set of architecture independent applications that are compatible with any type of device.

What actually fixes the situation is updating the sign-in credentials of the Jolla account on the device. That creates a new access token for the store client which in turn corrects the device associations on the store backend. So factory reset or other actions should not be necessary.

We will be investigating this further and hopefully will find the root cause.

edit flag offensive delete publish link more

Comments

3

Thanks for the explanation.

eson ( 2016-08-14 19:20:55 +0200 )edit

I had this exact same problem too, though it started after I switched between Jolla C and Jolla 1 with the same account.

Venty ( 2016-08-16 12:45:17 +0200 )edit
1

This workaround works for me. Problems started I think on my Jolla C after I started my Jolla 1 and put credential (it was reset to factory default, and I wanted to tests software on the old device). Hope that helps!

Smortex ( 2016-08-20 22:47:21 +0200 )edit

Question tools

Follow
2 followers

Stats

Asked: 2016-08-14 13:04:31 +0200

Seen: 283 times

Last updated: Aug 14 '16