That's when I realized that I had done three posts in a year.
#LAUNCHBAR GOOGLE CALENDAR UPDATE#
Once the issue was found, I came here to make a post about what the problem was and to let anyone who cared to know the issue was fixed and the update was available. When you go back to the purchase screen, the app will check to see if you own the extension and if you do, it will activate it (after doing this you may need to clear the app from the recent apps so it restarts).Įarlier in the month when the Yahoo geocoder I was using got deprecated, I had to go in to panic development mode (something I'm used to sadly). Someone who has already purchased and is willing to clear the data for the app.Someone who wants to purchase the extension (I have a couple people who have emailed me).So, I'm looking for two people to help me test. I also can't go though the purchase process even in a debug mode.
#LAUNCHBAR GOOGLE CALENDAR CODE#
However, I couldn't test that in a positive scenario (since I can't purchase my own extension), but I've seen the code check with the play store and see that it's not purchased. I've also checked the code for re-activating the extension if the data is reset. I've followed the coding example and I think it's good.
#LAUNCHBAR GOOGLE CALENDAR APK#
it seems that the APK (ie program) needs to be uploaded and published for the In App Purchase stuff to work. So, I've made the changes and tested as much as I can. I finished one project and before I start on something new, I decided to sit down and bang this out. I've meant to go back and fix it, but my time has been rather limited as I've been working on other side projects during my lunch (ie the time that 95% of DCP was written). January came and went and in app purchase for the dock extension stopped working. Back in January, Google deprecated version 2 of the in app purchasing API. However, it's pretty minor and probably doesn't affect most people other than me. last post here was (as you guessed) 273 days ago and yes, with this post comes an update to Desk Clock Plus. I never though that it would ever have been downloaded over 50,000 times and still have 9-10,000 installs. After that, who knows.īut the one thing I do want to do is thank everyone who has downloaded Desk Clock Plus and a big thank you to the people who threw a dollar at me for the extension. While that seems like a long time, remember that I'll be working on it less than an hour a day. I'll be starting on a fairly large project that will need to be completed by October(ish). However, over the past two years or so, I've started working more with a non-profit museum that I've belonged to for most of my life. It is one of those things that I want to get back to and do a proper re-write. NET developer that I am expects the = to work the same way.Īs usual, when I end one of these posts, I'll mention what the future holds for Desk Clock Plus. equals will become trivial, but for now the. My 9-5 job is slowly (and I do mean SLOWLY) starting to move into the world of web development using angular and java script and at that point comparing two string values using. The problem is that (for right now) I don't do java development and that's just how things work in java. Now, this is something very small and trivial and something that I potentially should have realized a lot faster. Would return false (even though they were the same string) but, So, I found the problem with the in app purchasing not verifying (the payload).
0 kommentar(er)
