When I said "last update" I meant the one previous to Marshmallow. Lollipop. When that one came out, I had no troubles.
As far as Eclipse over Android Studio... Yeah, shit happens. But if that's the way the waters a flowing, I'll have to get with it. Anyway.... Considering I haven't found anyone else complaining about this issue with the widgets, I've not gotten any reports from anyone using my apps, . I am assuming that it is something on MY device I haven't found anything with Google searches saying that 6.0 is to blame. If you wouldn't mind, and since I have your attention... Could you install one of my widgets and see if it updates on your device? https://play.google.com/store/apps/developer?id=Kenneth+Lawton That the list of all the stuff I have on Play. Go with the Moon Phase or one of the Countdown apps. On Monday, March 7, 2016 at 7:04:47 PM UTC-5, TreKing wrote: > > > On Mon, Mar 7, 2016 at 3:00 PM, Ken Lawton <[email protected] > <javascript:>> wrote: > >> These are apps that have been running with no trouble at all for like 2 >> years. Even when the last Android update came out, the widgets continued >> along as if nothing had changed. >> > > Didn't you say that all of your widgets started to fail to update after > you installed Marshmallow on your phone? > Now you're saying they continued to work as if nothing changed? Which is > it? > > >> There is no manner of debugging I can do if my current debugging >> environment doesn't show any problems at all. >> > > I don't know what that means. You said, if you first post, that you got > Marshmallow *on your device* and that the widgets failed to update. > Therefore, I would expect that you would be able to debug *your own app > on your own device.* > > >> I guess what I really want to know is if anyone is aware of changes to >> how the widget update handler works in 6.0 as opposed to every prior >> release. >> > > You can review > http://developer.android.com/about/versions/marshmallow/android-6.0-changes.html > But again - Android should run in compatibility mode. Even if they made > changes to Widgets from 6.0 forward, that should not effect current apps in > the wild. That would be A Dick Move™ on Google's part and would break > thousands of apps. > > >> In any case... I cannot even compile for 6.0 (23), unless I change my >> authoring environment. I've been using Eclipse all this time. When I >> tried to update that to the new set of SDKs, the whole thing broke. Then I >> find that the SDK is no longer supported with Eclipse. I have to change >> over to Android Studio. >> > > You should conceivably still be able to use Eclipse, but yeah, it's about > time your boarded the Android Studio train. > > >> Seriously... That is a serious pain in the arse. I like my environment >> just fine. And it took a long time to get comfortable with it. Only for >> them to say, "yeah, we're not gonna do that any more." >> Having said that, if that's what I have to do, then so be it. Just have >> to find the time to work it all out. >> > > Hey, nobody likes change, but shit happens. Technologies - and the tools > we use to create them - change and evolve. It's our responsibility as > developers to keep up. > > Good luck. > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/b2d2c83e-2965-4556-9865-e4073a66df1f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
