bug: Plugin creates error for Block editor screen

[eliastoowoxx454]

Bug Report

Plugin Version

3.6.1

PHP Version

8.2.27

WordPress Version

6.7.2

Bug description

When the Simple-JWT-Login plugin is installed, an error occurs. In the site health info of WordPress, I receive this error message:

"The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

When testing the REST API, an unexpected result was returned:

REST API Endpoint: {Domain}/wp-json/wp/v2/types/post?context=edit
REST API Response: (403) Forbidden"

After deactivating and reactivating my plugins, I discovered that the issue is caused by your plugin. This error results in the inability to create new pages, displaying a "Publishing Failed" error, and it also causes errors when updating existing content ("Updating Failed").

--> Further notice: Downgrading the plugin to version 3.6.0 resolved this error

What did you expect to happen? What actually happened?
Should work fine and not cause this error. Caused the publishing errors.

Other installed plugins (optional)

All-In-One Security (AIOS) – 5.4.0
App Favorites Sync – 1.0 // my custom plugin
Contact Form 7 – 6.0.5
Elementor – 3.28.3
Hide Admin Bar Based on User Roles – 5.2.0
LearnDash Custom API – 1.0
LearnDash LMS – 4.21.1
LearnDash LMS - Course Grid – 2.0.10
LearnDash LMS - Integrity – 1.2.1
LoginWP (Formerly Peter's Login Redirect) – 3.0.8.6
Microsoft JWT Auth – 1.0 // my custome plugin
Simple Custom CSS and JS – 3.50
Simple Local Avatars – 2.8.3
Simple-JWT-Login – 3.6.1
Under Construction – 4.02
User Role Editor – 4.64.4
WP Mail SMTP – 4.4.0

Additional Context (optional)

With activating and deactivating every plugin i found out that when your plugin is disabled everything works fine and i get no Error

[nicumicle]

Thank you @eliastoowoxx454 for reporting this issue.
I will handle it with high priority.

[nicumicle]

Hi @eliastoowoxx454,
I've released version 3.6.2.

Please update your plugin, and the issue should be fixed.