-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
Problem Calling CropImage.getActivityResult from Java #113
Comments
Hello @NmMedina welcome to the lib Please check this discussion We add some For this we need to add a Java Sample code, to be sure is working. Please feel free to add the Java Sample and open a PR for it |
Hi, @Canato Thanks for the fast response! Perfect I going to work on this example and make a PR |
Let this open, so people know you are working on this! Will link with the discussion |
Hello I really need help on this, my codes is full on java so need this library working on java too. What should I do to help you fix this bug? I still new in PR that you mentioned, trying to push my sample in separate branch but not working. Thank you |
Hey @junaediwidjojo thanks for being involved =D. To add a PR you will need to create a fork form the repository and create the PR from your forkRepo to this repo. The latest button is the one you wanna. Later you will be able to open a PR like this: As well, please take a read in the CONTRIBUTING GUIDE For this work we need some stuffs:
|
meanwhile this is simple workaround: |
CropImage.getPickImageChooserIntent, getPickImageResultUri also can`t be called from Java |
please open a PR or issue for this. |
Hi there I'm coming from the old repository due I'm having problems with Android 11 when accepting the Photo but when I'm trying to get the result from the activity I can't get the result due it's not static, reviewing the Java version has the static modifier
but the kt file doesn't have the @JvmStatic
Is the intended behavior? I cant figure out how to use that method, any advice will be welcome
The text was updated successfully, but these errors were encountered: