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

Package not working for me #13

Closed
AhmedHammad0900 opened this issue Mar 4, 2022 · 5 comments
Closed

Package not working for me #13

AhmedHammad0900 opened this issue Mar 4, 2022 · 5 comments

Comments

@AhmedHammad0900
Copy link

AhmedHammad0900 commented Mar 4, 2022

I am interested in this package

I used it as follows in documntion but it detected nothing ..

I used SHA1 that I got from gradlew signingReport command so I am not sure if it's the right way
it was under the following lines

 Task :app:signingReport
Variant: debug
Config: debug
Store: C:\Users\myuserhere\.android\debug.keystore
Alias: AndroidDebugKey
MD5: here is md5
SHA1: here is the one I used ..

image

image
`
image
image
image

    • Result on Emulator for app-relase Memu Emulator *

image

I did something wrong or there is a problem that emualtor not getting detected ? I know there is a different between debug and relase but not understanding if I did mistake relayed to that ... not professional to know that details

@talsec-app
Copy link
Member

Hello AhmedHammad0900.
Did you start Talsec using app.start() after providing config and callback in TalsecApp? It is not visible in your code snipets.
Talsec Team

@AhmedHammad0900
Copy link
Author

Hello AhmedHammad0900. Did you start Talsec using app.start() after providing config and callback in TalsecApp? It is not visible in your code snipets. Talsec Team

Yea I started it and got in Terminal , it worked for a while and stopped working and the problem is back in already Relased app idk how it happened ?

E/flutter (18753): #8 TalsecApp.start (package:freerasp/talsec_app.dart:66:5)

@talsec-app
Copy link
Member

talsec-app commented Mar 29, 2022

Please verify that you notified the framework that the internal state of those strings has changed by calling setState:

onRootDetected: () => {
  Root = 'Root detected';
  setState(() {});
}

Also check #11 (comment) if it helps you.

If the issue persists, please let us know. You can email us at info@talsec.app so we can look into it together.

Talsec Team

@talsec-app talsec-app reopened this Mar 29, 2022
@AhmedHammad0900
Copy link
Author

Please verify that you notified the framework that the internal state of those strings has changed by calling setState:

onRootDetected: () => {
  Root = 'Root detected';
  setState(() {});
}

Also check #11 (comment) if it helps you.

If the issue persists, please let us know. You can email us at info@talsec.app so we can look into it together.

Talsec Team

yea it was about setstate ty alot <3
but It don't work on IOS I am getting alot of errors ,, I edited scheme and added the script , also changed confirgations to recommended one for pods and runnder still getting the error

image

@talsec-app
Copy link
Member

Hello @AhmedHammad0900, we are sorry for the late response. Does the issue still persist? Could you elaborate more on exactly what errors (stack trace or screenshot)?

Are you trying to build the debug or release version? There is an issue with the release version not being able to run in Xcode Simulators (https://docs.flutter.dev/testing/build-modes#release)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants