-
-
Notifications
You must be signed in to change notification settings - Fork 616
Confirmation Dialog & Troubleshoot Guide to Tackle Webcam Permission Permanent Denial #1005
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
Draft
rohan-pandeyy
wants to merge
2
commits into
AOSSIE-Org:main
Choose a base branch
from
rohan-pandeyy:feat/webcam-confirmation-and-recovery
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| # Camera Permission Troubleshooting | ||
|
|
||
| This guide explains why camera access may become permanently blocked in PictoPy on Windows, and how to recover from it. | ||
|
|
||
| ## Why Camera Permission Gets Stuck | ||
|
|
||
| When you click **"Don't Allow"** on the camera permission prompt in PictoPy, the denial is **not** stored in Settings. Instead, it's stored by the app's internal web engine (WebView2) at the Chromium layer. | ||
|
|
||
| --- | ||
|
|
||
| ## Recovery Steps | ||
|
|
||
| ### Windows: | ||
|
|
||
| !!! warning "This is a destructive workaround" | ||
|
|
||
| > Deleting the WebView2 data folder will reset: | ||
| > | ||
| > - Camera permission (allowing re-prompt) | ||
| > - Onboarding state | ||
| > - Avatar/name selection | ||
| > - Any other local webview data | ||
| > | ||
| > Use this as a **last resort** only. | ||
|
|
||
| #### Step 1: Close PictoPy | ||
|
|
||
| Make sure PictoPy is completely closed before proceeding. | ||
|
|
||
| #### Step 2: Locate the WebView2 Data Folder | ||
|
|
||
| Open **File Explorer** and navigate to: | ||
|
|
||
| ``` | ||
| %LOCALAPPDATA%\org.aossie.pictopy | ||
| ``` | ||
|
|
||
| You can paste this path directly into the File Explorer address bar. | ||
|
|
||
| #### Step 3: Delete the `EBWebView` Folder | ||
|
|
||
| Right-click the `EBWebView` folder and select **Delete**. | ||
|
|
||
| #### Step 4: Restart PictoPy | ||
|
|
||
| Launch PictoPy again. When you try to use the webcam feature, you'll be prompted for camera permission again. | ||
|
|
||
| --- | ||
|
|
||
| ## Still Need Help? | ||
|
|
||
| If you're still experiencing issues after following these steps, please [open an issue on GitHub](https://github.com/aossie-org/PictoPy/issues/new?template=bug.yml) with: | ||
|
|
||
| - Your Platform (Windows, Linux, macOS) | ||
| - Steps you've already tried | ||
| - Any error messages you see | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add language identifier to the fenced code block.
The code block should specify a language identifier for proper syntax highlighting in the documentation.
📝 Proposed fix
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
34-34: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents