Status Update
No update yet.
Comments
ha...@gmail.com
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
ar...@notdot.net
ni...@gmail.com
"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"
ha...@gmail.com
pr...@google.com
I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨
st...@gmail.com
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.
an...@apps4u.co
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!
rp...@beneficiofacil.com.br
@
Thank you for the update @
ha...@gmail.com
Android 13 is out today and we still have no patch unlike what you said a month ago
an...@apps4u.co
rp...@beneficiofacil.com.br
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
ga...@gmail.com
- 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
ga...@gmail.com
br...@gmail.com
That must be some really intense testing as we are 10 days later and still nothing on sight. I don't want to be a P2 issue if that's what a P1 is.
Description
Traceback (most recent call last):
File "/home/user/bin/remote_api_shell.py", line 68, in <module>
run_file(__file__, globals())
File "/home/user/bin/remote_api_shell.py", line 64, in run_file
execfile(script_path, globals_)
File
"/home/user/in/appengine.d/googleappengine-trunk/python/google/appengine/tools/remote_api_shell.py",
line 95, in <module>
main(sys.argv)
File
"/home/user/in/appengine.d/googleappengine-trunk/python/google/appengine/tools/remote_api_shell.py",
line 80, in main
remote_api_stub.MaybeInvokeAuthentication()
File
"/home/user/in/appengine.d/googleappengine-trunk/python/google/appengine/ext/remote_api/remote_api_stub.py",
line 542, in MaybeInvokeAuthentication
datastore_stub._server.Send(datastore_stub._path, payload=None)
File
"/home/user/in/appengine.d/googleappengine-trunk/python/google/appengine/tools/appengine_rpc.py",
line 346, in Send
f = self.opener.open(req)
File "/home/user/local/python2.5/lib/python2.5/urllib2.py", line 387, in open
response = meth(req, response)
File "/home/user/local/python2.5/lib/python2.5/urllib2.py", line 498, in
http_response
'http', request, response, code, msg, hdrs)
File "/home/user/local/python2.5/lib/python2.5/urllib2.py", line 425, in
error
return self._call_chain(*args)
File "/home/user/local/python2.5/lib/python2.5/urllib2.py", line 360, in
_call_chain
result = func(*args)
File "/home/user/local/python2.5/lib/python2.5/urllib2.py", line 506, in
http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 302: Found