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
Need help in implementation as I am unable to stop screen capture #3
Comments
What is the behavior you are expecting when back in app? |
I am just expecting when user is in MyHomePage, user should not be able to capture screen shot or any screen recorder app should not be able to create video of that screen. |
Reason FLAG_SECURE was not working in my application was missing following in AndroidManifest application tag:
With your library it started "could not capture screen shot" To stop any screen recorder from capturing video of my app , I had use code to secure surface view.
|
Sorry I missed the part where you said that it was in the demo app that it was working. Tbh I never tried without v2 embedder but it shroud work as I also have the v1 register method: companion object {
@JvmStatic
fun registerWith(registrar: Registrar) {
val channel = MethodChannel(registrar.messenger(), "secure_application")
channel.setMethodCallHandler(SecureApplicationPlugin())
}
} I will try to test with old embedding to try to reproduce your issue. FYI on Android I also use native for app switcher / screenshot protection: Line 83 in a2ecc9b
|
I understand that you have also use native method.
I really liked your library and simplicity of it to use. |
I have tried to implement your library as per documentation instructions.
But When I use your demo app , I am unable to capture screen and also any screen recorder app don't capture app screen , just black screen AS it should be.
But In my app it never works.
Please guide me what step I am missing.
My code :
As per my understanding of your library , I want to secure the screen and don't want to lock the screen.
I guess I am missing some step.
Plese guide me to solution.
The text was updated successfully, but these errors were encountered: