New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWSCloudWatchProvider writes infinity number of errors if user doesn't have permissions to write logs to CloudWatch #9575
Comments
May be related to my bug: #10172 Possibly will need to refactor AWSCloudWatchProvider._getNextSequenceToken, move out |
Thank you for the feedback @dapriett - I am going to close your issue and use this one for our team to investigate it further. Thank you for referencing it! |
Commenting to give update on this issue after seeing #10891 opened recently. We are marking these issues tied to |
This issue still exists, FYI. |
Hi @DaryBeattie - we are planning on introducing a revamped version of our CloudWatch logger, which will also enable you change your logging configuration remotely as well. You can see an example of it that is available for Swift and Android developers. |
Hi Abdallah,
Thanks for responding about my issue.
That's great, yes -- and I did see that article already and read it. :)
But the big question after I read that was: does it, or *will it*, work
with React Native?
Sincerely,
Daryl.
…On Thu, Aug 10, 2023 at 11:08 PM Abdallah Shaban ***@***.***> wrote:
Hi @DaryBeattie <https://github.com/DaryBeattie> - we are planning on
introducing a revamped version of our CloudWatch logger, which will also
enable you change your logging configuration remotely as well. You can see
an example of it that is available
<https://aws.amazon.com/blogs/mobile/aws-amplify-cloudwatch-logger-is-now-available-for-swift-and-android/#:~:text=We%20are%20excited%20to%20announce,different%20parts%20of%20your%20app.>
for Swift and Android developers.
—
Reply to this email directly, view it on GitHub
<#9575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZYETGR6LWVJEXJS2I5ALP3XUWO4VANCNFSM5ODPALSA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, we are planning to have it work with React Native as well! |
And another big question....
I just logged this bug:
#11785
Will this new logger make that bug completely obsolete?
(I thought you were replying about my new bug, but it appears you were not!)
- Daryl.
…On Thu, Aug 10, 2023 at 11:27 PM Daryl Beattie ***@***.***> wrote:
Hi Abdallah,
Thanks for responding about my issue.
That's great, yes -- and I did see that article already and read it. :)
But the big question after I read that was: does it, or *will it*, work
with React Native?
Sincerely,
Daryl.
On Thu, Aug 10, 2023 at 11:08 PM Abdallah Shaban ***@***.***>
wrote:
> Hi @DaryBeattie <https://github.com/DaryBeattie> - we are planning on
> introducing a revamped version of our CloudWatch logger, which will also
> enable you change your logging configuration remotely as well. You can see
> an example of it that is available
> <https://aws.amazon.com/blogs/mobile/aws-amplify-cloudwatch-logger-is-now-available-for-swift-and-android/#:~:text=We%20are%20excited%20to%20announce,different%20parts%20of%20your%20app.>
> for Swift and Android developers.
>
> —
> Reply to this email directly, view it on GitHub
> <#9575 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AZYETGR6LWVJEXJS2I5ALP3XUWO4VANCNFSM5ODPALSA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
We will fix this bug as well, Daryl! |
Wow, uh… honestly you made my day. 🙂
Thank you!!!
- Daryl.
…On Thu, Aug 10, 2023 at 11:36 PM Abdallah Shaban ***@***.***> wrote:
We will fix this bug as well, Daryl!
—
Reply to this email directly, view it on GitHub
<#9575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZYETGQL5GAVUH66Y3EIRNLXUWSDLANCNFSM5ODPALSA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Before opening, please confirm:
JavaScript Framework
Angular
Amplify APIs
Not applicable
Amplify Categories
Not applicable
Environment information
Describe the bug
If user doesn't have permissions to write logs to AWS CloudWatch then AWSCloudWatchProvider infinitely write errors to console
I didn't find an ability to set maximum attempts for logging operation.
Expected behavior
There must be a setting to prevent infinity errors if
AWSCloudWatchProvider
can't write logs to AWS CloudWatchReproduction steps
AWSCloudWatchProvider
based on information in PR: Core/cloudwatch logging #8309info
:Code Snippet
// Put your code below this line.
Log output
aws-exports.js
No response
Manual configuration
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: