Status Update
Comments
si...@google.com <si...@google.com>
si...@google.com <si...@google.com> #2
Information redacted by Android Beta Feedback.
ph...@gmail.com <ph...@gmail.com> #3
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
si...@google.com <si...@google.com> #4
Exe
ph...@gmail.com <ph...@gmail.com> #5
Thank you for reporting this issue. We have a fix rolling out in an upcoming release.
si...@google.com <si...@google.com> #6
ph...@gmail.com <ph...@gmail.com> #7
ph...@gmail.com <ph...@gmail.com> #9
the situation will roll back ???
P.
On Tue, May 24, 2022 at 3:04 PM <buganizer-system@google.com> wrote:
si...@google.com <si...@google.com> #10
Hello,
-
The engineering team has confirmed that the change in format will be backward compatible, so that both the formats
.received_message.message.attributes.objectId
and.message.attributes.objectId
can be used. -
They will Fix the backward compatibility for gcloud pull json format response and will also add the json format unit tests for gcloud pubsub subscriptions pull.
ph...@gmail.com <ph...@gmail.com> #11
So it is good for me.
si...@google.com <si...@google.com> #12
Hello,
Since you have confirmed that the issue is resolved, I am marking this issue as fixed.
However, if you still face any issue, please don’t hesitate to raise a new thread describing the issue.
Description
I have noticed a change in the event message structure.
I need to use ".received_message.message.attributes.objectId". to reach objectid on 375.
on 374 it was ".message.attributes.objectId"
Didn't find any notice or documentation about this change.
Is it normal???
Have a good day,
P.