Support for all HTTP methods [35877350]

Assigned

Feature Request

Status Update

No update yet.

Description

on...@gmail.com

created issue #1

Jan 9, 2009 12:06AM

What steps will reproduce the problem?
1. Send e.g. a PROPFIND request (any WebDAV client should do that)

Does this problem exist with both the SDK app server and our production app
servers?
Yes

What is the expected output? What do you see instead?
I'd expect AppEngine to call the handler specified in app.yaml. Instead,
both dev_appserver and the production server completely ignore the request,
giving me no chance to handle it. The log contains ERROR: "code 501,
message Unsupported method ('PROPFIND')". Note that I'm not talking about
the webapp framework, this is an issue with the server itself.

What version of the product are you using? On what operating system?
1.1.7 / Ubuntu Linux 8.10

Please provide any additional information below.
Support for all HTTP methods (incl. PROPFIND) is required in order to
implement WebDAV functionality

Comments

js...@gmail.com <js...@gmail.com> Jan 12, 2009 09:40PM

Assigned to js...@gmail.com.

ch...@gmail.com <ch...@gmail.com> #2May 20, 2010 07:52PM

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

no...@google.com <no...@google.com> #3May 22, 2010 11:39PM

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.

jo...@gmail.com <jo...@gmail.com> #4Aug 16, 2010 07:05PM

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

dev_appserver-allmethods.patch

984 B

View

Download

no...@gmail.com <no...@gmail.com> #5Aug 17, 2010 10:53AM

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

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

nf...@gmail.com <nf...@gmail.com> #6Sep 22, 2010 03:09PM

+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

nf...@gmail.com <nf...@gmail.com> #7Dec 2, 2010 10:58PM

Note that I've been able to make it work by:

Adding <action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> in the intent filter
Removing <data android:scheme="wear" android:host="*" />

But I feel like this is not something we should do

nf...@gmail.com <nf...@gmail.com> #8Aug 17, 2011 06:07PM

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

pr...@google.com <pr...@google.com> #9Aug 27, 2011 12:49AM

If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.

But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.

pe...@gmail.com <pe...@gmail.com> #10Nov 17, 2011 04:41PM

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!

nf...@gmail.com <nf...@gmail.com> #11Nov 17, 2011 10:44PM

@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

[Deleted User] <[Deleted User]> #12Mar 18, 2012 03:21AM

Hey @

comment#10

, do you have any news to share?

Android 13 is out today and we still have no patch unlike what you said a month ago

[Deleted User] <[Deleted User]> #13Mar 18, 2012 03:22AM

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.

[Deleted User] <[Deleted User]> #14Nov 15, 2012 03:16AM

This issues has been already given high priority (updated external priority on this bug to reflect internal status). The fix is on the way and going through the final rounds of testing, so the roll out is slated to next couple of weeks.

To reiterate what have been mentioned earlier on this bug: this issue affects only apps targeting Android 13, so the apps won't break unless you bump targetSDK version to 33. In case if you want to start working on app compatibility for Android 13 behaviour changes, you could use Compatibility framework to toggle on/off the changes individually for isolated testing.

si...@gmail.com <si...@gmail.com> #15Apr 29, 2014 12:16PM

comment#14

as much as I agree that is not a blocking bug, you need to understand that:
- The report is 2 months old
- Google chose to release Android 13 with that bug
- There's no mention of this bug on the documentation so you can totally bump your targetSdk without noticing it

So thank you guys for working on this but it's still not a valid excuse for taking that long for such an important issue. Now that being said, let us know when a fix is available