I have ceased producing new apps or updating my current ones due to an extremely awful effort / income relationship of my apps in both stores, i.e.
There won’t be any more steps taken from me, due to the following reasons: I have unpublished Google+Plus from the Windows Phone store. I am sorry if the issues still persist for some users. Still, I will continue to enhance the memory usage of the app (which is still not optimal) and create new features, as difficult as it may seem (because of the limited API). I understand that some people may have ceased to use the app when experimenting the first version and that may have led to less app usage and consequently a lower number of crashes, but the coincidence of the release and the major drop in crashes cannot be denied.īecause of that, along with some recent reports of a good experience when using the app, I believe that the worst crashes are now over and everyone who used the app at the beginning should give it a shot again. I am making this post at this very moment and not sooner because I have been monitoring this value in the last two weeks. Ever since that date, the crash count dropped immediately from hundreds to tens and later to very few and even 0 everyday, up until now.
Google talk app for windows 8.1 update#
That update was launched on the 23rd of February. in the crash reports I could clearly see that indeed the app was generating a lot of crashes (more than 1.5k in just 10 days).Īs I told you before, I made an update to the app that consciously addressed memory leaks (that in the end led to crashes) but not the crashes themselves / directly.
When I first launched the app, the crashes that you talked about were confirmed by the DevCenter, i.e. I will also try to take a closer look at the live tile, something which starts in the home page (and not login page) and could be the source of the problem I will possibly disable the live tile at least to see if things improve from then on. Part of that optimization was the complete removal of maps (the MapControl has a lot of problems if added dynamically), so I'm sorry for that. I have fixed that and you should be able to extend your experience using the app much longer (technically the memory leak still exists if you use the app for a LONG time). I did manage to optimize the app last week since there was a memory leak causing it to crash within just a few navigations (around 10 or 15 depending on the number of items in activity lists). I use the least specced simulators (512Mb) and my real device too, a Lumia 1320, which is not high-end in any way as I'm sure you know. The ultimate fact is that I simply cannot crash the app in any of the scenarios that people have been providing (here and in other places too): splash screen, logging in or any process which makes the app lose focus.
I am very sorry for the trouble you have been having using my app.
0 kommentar(er)
