-
Notifications
You must be signed in to change notification settings - Fork 231
I am experiencing issues using 1.5.2. #152
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
Comments
@stevkan |
In my case:
|
I just experienced some issues with version 1.5.2 and I had to rollback to 1.4.0. When I do the following call:
It is not returning the promise, never. I put some debugging |
@muthurathinam, apologies. I somehow missed your message to me way up above. It still does not work for me unless I use v1.0.0 (have tried up to v1.7.0). Please let me know if there is specific information you would like/need from me. p.s. I'll keep this on my radar, this time around. |
@stevkan can you help with this, just verify whether you are getting the same error that you have mentioned here.
Also, you have mentioned that Downgrading to 1.4.0 and the API calls succeed (in the issue description) but this contradicts your above comment can you please clear things out for me. FYI: This is autoclosed when I did mention the issue in the PR and also the fix is not released yet. will post here once its released. |
@muthurathinam, apologies for the confusion. Yes, I am still receiving the above error using version 1.5.2. Using version 1.4.0 does work (I believe that was a typo - 1.0.0 should have been 1.4.0). As an aside, when I try version 1.7.0 I get the following error (happy to log as a new issue):
The 'onTurnError' text can be ignored. The important part is the reference to 'displayName' which occurs when trying to authenticate. |
I am also experiencing issues using 1.5.2.
Description
API calls using 1.5.2 fail with "Response is not defined". In my case, this is true whether using API version "v1.0" or "beta". Here are the calls I am making and the (same) resultant error that is produced after each.
Downgrading to 1.4.0 and the API calls succeed.
Console Errors:
Steps to Reproduce
Expected behavior:
Values should be returned via MS Graph for the various API calls.
Actual behavior:
Receive "Response is not defined" error.
Originally posted by @stevkan in #151 (comment)
The text was updated successfully, but these errors were encountered: