Skip to content
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

Error when offline.access scope is not specified #63

Closed
myConsciousness opened this issue Jan 30, 2023 · 0 comments · Fixed by #64
Closed

Error when offline.access scope is not specified #63

myConsciousness opened this issue Jan 30, 2023 · 0 comments · Fixed by #64
Assignees
Labels
bug Something isn't working

Comments

@myConsciousness
Copy link
Member

1. Current bug behavior

[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: Null check operator used on a null value
#0      PlaygroundHomePage._fetchAccessToken (package:twitter_api_playground/src/service/view/home/home_page.dart:289:40)
<asynchronous suspension>
#1      PlaygroundHomePage.build.<anonymous closure> (package:twitter_api_playground/src/service/view/home/home_page.dart:49:31)
<asynchronous suspension>

2. Expected behavior

3. Steps to reproduce

4. Flutter doctor output

Output of: flutter doctor -v

5. More environment information

6. Log information

Enter log information in this code block

7. More information

@myConsciousness myConsciousness added the bug Something isn't working label Jan 30, 2023
@myConsciousness myConsciousness self-assigned this Jan 30, 2023
@myConsciousness myConsciousness linked a pull request Jan 30, 2023 that will close this issue
7 tasks
bors bot added a commit that referenced this issue Jan 30, 2023
64: fix: fixed for the issue (#63) r=myConsciousness a=myConsciousness

# 1. Description

<!-- Provide a description of what this PR is doing.
If you're modifying existing behavior, describe the existing behavior, how this PR is changing it,
and what motivated the change. If this is a breaking change, specify explicitly which APIs have been
changed. -->

## 1.1. Checklist

<!-- Before you create this PR confirm that it meets all requirements listed below by checking the
relevant checkboxes (`[x]`). This will ensure a smooth and quick review process. -->

- [x] The title of my PR starts with a [Conventional Commit] prefix (`fix:`, `feat:`, `docs:` etc).
- [x] I have read the [Contributor Guide] and followed the process outlined for submitting PRs.
- [x] I have updated/added tests for ALL new/updated/fixed functionality.
- [x] I have updated/added relevant documentation in `docs` and added dartdoc comments with `///`.
- [x] I have updated/added relevant examples in `examples`.

## 1.2. Breaking Change

<!-- Does your PR require users to manually update their apps to accommodate your change?

If the PR is a breaking change this should be indicated with suffix "!"  (for example, `feat!:`, `fix!:`). See [Conventional Commit] for details.
-->

- [ ] Yes, this is a breaking change.
- [x] No, this is _not_ a breaking change.

## 1.3. Related Issues

<!-- Provide a list of issues related to this PR from the [issue database].
Indicate which of these issues are resolved or fixed by this PR, i.e. Fixes #xxxx* !-->

<!-- Links -->

[issue database]: https://github.com/twitter-dart/twitter-oauth2-pkce/issues
[contributor guide]: https://github.com/twitter-dart/twitter-oauth2-pkce/blob/main/CONTRIBUTING.md
[style guide]: https://github.com/twitter-dart/twitter-oauth2-pkce/blob/main/STYLEGUIDE.md
[conventional commit]: https://conventionalcommits.org


Co-authored-by: myConsciousness <contact@shinyakato.dev>
@bors bors bot closed this as completed in #64 Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant