-
Notifications
You must be signed in to change notification settings - Fork 39
RateMyApp resets after app update #44
Comments
Hi @sensboston, the fix is likely in the source code but there has not been a formal release since v1.1 ... In which type of project have you tried the control now? And which version? From NuGet or your own build? Such info is mandatory for being able to reproduce and fix the issue. |
Hi Lucian, I'm using build from the source code ('cause NuGet build has a bug preventing XAML rendering in Visual Studio). Probably it's not a bug (I mean «automatic reset») but feature but I'll like to completely disable that «feature» - it's already costs me a few good reviews :( This behavior is really annoying. So, the “automatic reset” exists in all versions (I’ve tried 1.0, 1.1 & 1.2 beta); the XAML bug exist in NuGet packages (old and latest one). WBR, Sergey From: Lucian Tomuta [mailto:[email protected]] Hi @sensboston https://github.com/sensboston , the fix is likely in the source code but there has not been a formal release since v1.1 ... In which type of project have you tried the control now? And which version? From NuGet or your own build? Such info is mandatory for being able to reproduce and fix the issue. — |
Hi @sensboston There are two known issues that may appear to make the control as if it was reset. The fact that data is not saved if the app exits by calling Terminate (fixed in code now, in alpha NuGet build only for SL8.1) and a bug that affects the apps using a day counter (not fixed as far as I can remember).b Whether we are talking about one of these issues or a new one, I would need info about how to reproduce the bug. If you have a project you can share, please do. BR, |
It looks like the control resets itself and starts asking customers again and again after each app update. It's VERY ANNOYING behaviour and should be fixed as soon as possible (because many customers - who's already rated and reviewed my apps - become very angry).
Also, the latest NuGet update doesn't resolves issues #29 (marked as resolved!) and #41.
P.S. Note to author: your control is heavily advertised (and pushed to use by developers) by DVLUP site - they have actually a special update challenge. So PLEASE fix the bugs - it's not just a "indie" third-party control but the OFFICIAL and RECOMMENDED by Nokia/Microsoft control.
The text was updated successfully, but these errors were encountered: