Management/Billing/Quota API [35876599]

Assigned

Feature Request

Status Update

No update yet.

Description

pa...@gmail.com

created issue #1

Dec 3, 2008 08:38AM

I would like there to be an Index API that can be used to create indexes
and manage indexes programmatically without the need for me to manage an
index.yaml file outside the application and upload a new version of the
application each time I need to change the application.

I am in the situation where I can dynamically define properties, either
expando or as a datastore.Entity but I cannot allow a user to perform a
query that would include a range query on a property or alter the sort
order against these properties in a user defined query.

From an application point of view, I can handle the fact that an index
might take to generate and may not be available for some time.

Comments

ma...@google.com <ma...@google.com> Dec 15, 2008 11:36PM

Assigned to ma...@google.com.

ag...@gmail.com <ag...@gmail.com> #2Feb 26, 2010 05:11PM

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

ti...@gmail.com <ti...@gmail.com> #3Mar 12, 2010 10:49PM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

mi...@gmail.com <mi...@gmail.com> #5Dec 6, 2010 09:21PM

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

da...@gmail.com <da...@gmail.com> #6Dec 31, 2010 01:24PM

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

ke...@workiva.com <ke...@workiva.com> #10Dec 18, 2012 08:03PM

As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!

do...@gmail.com <do...@gmail.com> #11Jan 19, 2013 04:34PM

@comment#9 The Play Store will eventually require targeting API 33, then 34, etc, so accepting this regression in a customer release would be a time ticking bomb for Wear OS apps.

Thank you for the update @comment#10

kl...@google.com <kl...@google.com> #13Jul 15, 2016 07:49PM

I have no words for this. Android 13 is labeled "stable" but the Wearable API just doesn't work. Can't this issue be given higher priority? If you want to push WearOS you need to make sure it works normally.