This repository has been archived by the owner on Oct 10, 2024. It is now read-only.
Explain in the DOC what to find in the DOM, in case the camera doesn't show up #151
Comments
|
Okey, after digging a bit more, this should be the element we should see appearing in the DOM, just under the <body>
<!-- ... -->
<div style="position: absolute; left: 0px; top: -2px; height: 1px; overflow: hidden; visibility: hidden; width: 1px;"><span style="position: absolute; font-size: 300px; width: auto; height: auto; margin: 0px; padding: 0px; font-family: Roboto, Arial, sans-serif;">BESbswy</span></div>
<!-- ... -->
</body>For me it wasn't appearing at all, so I did try to move the logic in the |
|
This was something else, basically nothing will be shown in the DOM |
thegnuu
pushed a commit
that referenced
this issue
Sep 5, 2022
Added more detailed troubleshooting, with a fix for the following #151
thegnuu
added a commit
that referenced
this issue
Nov 18, 2022
* ⬆️ Bump minimist from 1.2.5 to 1.2.6 (#112) Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. - [Release notes](https://github.com/substack/minimist/releases) - [Commits](https://github.com/substack/minimist/compare/1.2.5...1.2.6) --- updated-dependencies: - dependency-name: minimist dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Reset last scanned code when resuming scan (#116) * Update BarcodeScanner.java reset scanResult after calling resumeScan * Update Plugin.swift reset scan result after calling resumeScan * 2.1.1 * fix IOS orientation (#131) Steps to reproduce : open the app in portrait/landscape mode => rotate => open the camera Issue the CameraView was being loaded when the app starts not with each scan. Somehow the cameraView doesn't recognize that the app has rotated * Capacitor v4 (#143) * feat(capacitor): update to capacitor v4 * fix(ios): small bugfixes * fix(ios): added self. to savedCall in scan() (#142) Co-authored-by: Kristof Hauser <hauser.kristof@gmail.com> * 3.0.0 * Add more detailed troubleshooting to the README (#152) Added more detailed troubleshooting, with a fix for the following #151 * fix(readme): typos and other enhancements * iOS interface orientation obsolete (#146) On iOS the `UIApplication.shared.statusBarOrientation` is deprecated and on newer versions obsolete. It has been replaced by code suggested here: https://askcodes.net/coding/-statusbarorientation--was-deprecated-in-ios-13-0-when-attempting-to-get-app-orientation #129 * fix(readme): added ionic stuff * updating definitions * adding dependencies * updating permisions * feat: Adding ML-Kit Logic * updating XML Layout * adding base for graphic drawing Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: PaintedShepherd <painted.shepherd@gmail.com> Co-authored-by: Yannik Ache Eicher <ache@bbit.io> Co-authored-by: Mohamed Abdelgwad <4671486+scr2em@users.noreply.github.com> Co-authored-by: Kristof Hauser <hauser.kristof@gmail.com> Co-authored-by: Raphaël Balet <raphael.balet@outlook.com> Co-authored-by: Robin <rattenval@hotmail.com> Co-authored-by: Abdulaziz Alghamdi <a.alghamdi@juleb.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
Actually, when running
BarcodeScanner.startScan()the camera does not show up.I tried to debug & fix with the following #7 (comment) or #26 as explained in the doc, but some of the information written are for over a year and doesn't seems to fit the solution anymore.
I've tried to do the thing with the background color to the
<html>element but couldn't find it.Describe the solution you'd like
Add in the documentation what we're expected to see in the DOM, to know if we do have indeed it loaded correctly
Describe alternatives you've considered
Could also provide step, in the doc, to know directly what to do instead as reading the issue through and trying outdated solution.
Additional context
Maybe it should have been a bug report, not sure though
The text was updated successfully, but these errors were encountered: