Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 2 days, 23 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 3 days, 22 hrs ago - more...
Kallela |
2012-02-20
, 14:36
|
|
Posts: 49 |
Thanked: 93 times |
Joined on Jan 2012
@ Finland
|
#11
|
Originally Posted by juhapekka
Hmm, that's strange too. I have also multiple Harmattan devices and if using the same Nokia account on them, I can install the once paid application to all of them. So it should work like you were expecting as the download & purchase history is tied to your Nokia account, not to you device. There is definitely some weird Store bug that you are now suffering from! Hopefully your filed bug report will be worked on.
|
|
2012-02-20
, 14:48
|
|
Posts: 115 |
Thanked: 188 times |
Joined on Feb 2006
@ Finland
|
#12
|
Originally Posted by caco3
http://www.developer.nokia.com/Commu...-free&p=883230
Beside of all, I suggest to post your question at http://www.developer.nokia.com/Commu...to-Nokia-Store
| The Following User Says Thank You to juhapekka For This Useful Post: | ||
|
|
2012-02-20
, 14:51
|
|
Posts: 49 |
Thanked: 93 times |
Joined on Jan 2012
@ Finland
|
#13
|
Originally Posted by caco3
If there really is such a limitation, it has to be more that that.
I read somewhere that you can download an app only 5 times before you have to repay it.
I as a publisher would like that people only have to pay once, unless I explicitly want them to repay (i.e. major update). I also often publish minor updates.
I have published one paid application and I have re-installed it more than 5 times from Ovi Store. While developing some new version, I will of course use Qt Creator to deploy the latest build on my device. However, before submitting the app to Store, I will always remove the development version and install the previous version from the Store and then do the update when it's available for the customers to see that the update really goes smoothly and the released version works for sure. Also because of reflashing the device, I have reinstalled paid applications a couple of times.
|
|
2012-02-20
, 14:57
|
|
Posts: 49 |
Thanked: 93 times |
Joined on Jan 2012
@ Finland
|
#14
|
Originally Posted by juhapekka
Ahaa! Could this fact be the root cause here for your explained behaviour? There were actually some warning post on N9 Developer blog recently advising not to change a published Store item from free to non-free, but to create a new item instead:
I guess the only difference what I have done is that I have changed from Free to Paid the price point and vice versa. So maybe something has gone bad in ovi store because of that.
http://www.developer.nokia.com/Commu...ate-experience
Maybe you should contact Ovi Publishing directly via email?
| The Following User Says Thank You to Kallela For This Useful Post: | ||
|
|
2012-02-20
, 16:33
|
|
Posts: 115 |
Thanked: 188 times |
Joined on Feb 2006
@ Finland
|
#15
|
Originally Posted by Kallela
Maybe this is the case, but still it should not happen. And if this is the case then the price point change from Free <> Paid should not be allowed at all.
Ahaa! Could this fact be the root cause here for your explained behaviour?
Originally Posted by Kallela
I did also contact them, but as it takes few days to get answers, I wanted to share the frustration and to see if I am alone with this issue. As I think that there is nothing that I can do to fix this, except not to do those free <> paid switching. But still as even those are approved by the Nokia Store QA then they should not allow them if this causes issues :/
Maybe you should contact Ovi Publishing directly via email?
 |
|
2012-02-20
, 17:01
|
|
Posts: 2,448 |
Thanked: 9,523 times |
Joined on Aug 2010
@ Wigan, UK
|
#16
|
Originally Posted by Kallela
I know the download limit was increased to 10 for Symbian applications. Perhaps this also applies to Harmattan applications. In any case, I agree with the earlier comment that download limits should be abolished. They are a menace and do nothing but cause headaches for both customers and publishers.
If there really is such a limitation, it has to be more that that.
I have published one paid application and I have re-installed it more than 5 times from Ovi Store. While developing some new version, I will of course use Qt Creator to deploy the latest build on my device. However, before submitting the app to Store, I will always remove the development version and install the previous version from the Store and then do the update when it's available for the customers to see that the update really goes smoothly and the released version works for sure. Also because of reflashing the device, I have reinstalled paid applications a couple of times.
__________________
'Men of high position are allowed, by a special act of grace, to accomodate their reasoning to the answer they need. Logic is only required in those of lesser rank.' - J K Galbraith
My website
GitHub
'Men of high position are allowed, by a special act of grace, to accomodate their reasoning to the answer they need. Logic is only required in those of lesser rank.' - J K Galbraith
My website
GitHub
 |
|
2012-02-20
, 19:52
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#17
|
So far I had no problems with updating or redownloading paid content. I only had to pay once, even if installing on another device.
Aborted music downloads could also be finished with Ovi Music. The downloads disappear from the transfer lists, but downloading the missing items doesn't charge again. If you don't trust the N9 client, you can also access Ovi Music via a webbrowser to complete the downloads.
Aborted music downloads could also be finished with Ovi Music. The downloads disappear from the transfer lists, but downloading the missing items doesn't charge again. If you don't trust the N9 client, you can also access Ovi Music via a webbrowser to complete the downloads.
__________________
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
| The Following User Says Thank You to pycage For This Useful Post: | ||
|
|
2012-02-21
, 13:32
|
|
Posts: 49 |
Thanked: 93 times |
Joined on Jan 2012
@ Finland
|
#18
|
Originally Posted by juhapekka
Yeah, this is definitely a bug in their system and should not happen!
Maybe this is the case, but still it should not happen. And if this is the case then the price point change from Free <> Paid should not be allowed at all.
|
|
2012-03-06
, 06:13
|
|
Posts: 115 |
Thanked: 188 times |
Joined on Feb 2006
@ Finland
|
#20
|
"I have seen cases where the pay button has appeared in the N9 store client
instead of the update button as that may confuse end customers by causing them
to think that they are paying for the upgrade. Once they have clicked on the
paid button the update process occurs but no payment is actually processed so
the end user doesn't actually get charged."
"I was able to confirm that the users who left the reviews did not get charged
twice for QAD Internet Radio Recorder (ID:249692) or QAD File Manager
(ID:174900)."
And they still say that they are investigating the store process.. I just wonder if anything will happen to this.
This totally blows..
I updated the open bug as well..
https://harmattan-bugs.nokia.com/show_bug.cgi?id=942
instead of the update button as that may confuse end customers by causing them
to think that they are paying for the upgrade. Once they have clicked on the
paid button the update process occurs but no payment is actually processed so
the end user doesn't actually get charged."
"I was able to confirm that the users who left the reviews did not get charged
twice for QAD Internet Radio Recorder (ID:249692) or QAD File Manager
(ID:174900)."
And they still say that they are investigating the store process.. I just wonder if anything will happen to this.
This totally blows..
I updated the open bug as well..
https://harmattan-bugs.nokia.com/show_bug.cgi?id=942
