PDA

View Full Version : [Solved] Jolla store: stubborn update notifications

gsalone
2014-01-14, 14:09
I have this problem with persisting notifications about updates in Friends and VLS remote applications. I have installed latest versions from Jolla store, tried to uninstall, restart and install again, I still get notification that they need updating..
I try to update, but they cannot update, they are already in latest version. All I get is "Problem with installing harbour-friends blah blah", and still these apps are marked as having update!

Any idea how to fix this? it is really frustrating as it appears in both lockscreen as notification, in notifications view of course, as well as in Jolla store. :confused:

EDIT:
This can be fixed permanently only when the Jstore approves and provides latest version of any app, so it is in sync with openrepos.
Otherwise, for each app, one manual solution is to delete specific repo it belongs to, and add version that is available from Jstore.
zypper rr <name_of_repo>
pkcon refresh
pycage
2014-01-14, 17:52
Did you happen to install these apps from sources outside the store as well?

Usually the store gives an update notification if it finds that the version of the package on the device is different from the one reported by the store server to be the current one.

Can you check the rpm package versions? If you have developer mode enabled.

rpm -qa | grep friends


Then compare this version with what the store shows for "Version". Tap on the app description text once to reveal the version info.
gsalone
2014-01-14, 18:00
rpm -qa | grep friends
harbour-friends-0.1.13-1.32.1.armv7hl

Store offers 0.1.9-1.26.1

And to this list, also now added MKpokerplaning and kitchen timer.. all offering updates, but already latest installed.
So to clean JStore's cache?
pycage
2014-01-14, 18:11
For Kitchen Timer, store tells me it's 0.1-1. I have no update notification.
rpm reports the same version.

What versions does it show you for Kitchen Timer?

If you close the store window, the store cache will clear after a few minutes. At least then it should show have the latest version info from the server.
gsalone
2014-01-14, 18:38
For Kitchen Timer, store tells me it's 0.1-1. I have no update notification.
rpm reports the same version.

What versions does it show you for Kitchen Timer?

If you close the store window, the store cache will clear after a few minutes. At least then it should show have the latest version info from the server.

I close, i wait, i restart, store's cache is not clearing..

Yes, also for Kitchen Timer, store tells me it's 0.1-1, but I have already installed 0.1-1.

And yes, as i said, I have all latest versions for all these apps installed, but store keeps thinking i need to update to the same latest already installed version.
pycage
2014-01-14, 18:40
OK, that's weird then. Maybe some race condition in the update detection.
J4ZZ
2014-01-14, 19:43
A simple phone reboot fixed it for me.
Got the friends (together with warehouse client) update via pkcon update before jolla store could download and install.
gsalone
2014-01-14, 21:21
A simple phone reboot fixed it for me.
Got the friends (together with warehouse client) update via pkcon update before jolla store could download and install.

How did you manage to get them updated before jolla store?
J4ZZ
2014-01-14, 22:06
I added most of the openrepos with 'zypper ar' to my repositories before the Warehouse client was even available....
So a
pkcon refresh
pkcon get-updates
pkcon update

updates both harbour and openrepos packages for me...

For example see: How to add NielDK's repo to SailfishOS (https://openrepos.net/user/500/repository)

Regards,

J4ZZ
gsalone
2014-01-14, 22:11
OK, I see your point.

But problem is that latest versions are already installed, it is just JStore that thinks they are not...
J4ZZ
2014-01-14, 22:40
You're right update notification just came back (didn't saw it while offline)... :(


J4ZZ
J4ZZ
2014-01-14, 23:26
Update: this worked for me. (http://talk.maemo.org/showpost.php?p=1406480&postcount=104) ;)
gsalone
2014-01-15, 08:03
And to me, worked the fact that the latest version was finally approved in Jstore and was available in jstore :)

So i think this is a Jstore bug in general.
pycage
2014-01-15, 17:53
Update: this worked for me. (http://talk.maemo.org/showpost.php?p=1406480&postcount=104) ;)

Ah, that explains a lot! :D
Thanks for sharing.