-
Notifications
You must be signed in to change notification settings - Fork 5
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
NPE on stopping the recorder #33
Comments
@3akat this was not crashing when we were using |
To help you out, you can reproduce the issue with these options: HashMap<String, String> extras = new HashMap<>();
extras.put("data", "{ \"foo\": \"bar\" }");
extras.put("title", "Tell me about a situation in which you had to solve a very difficult problem?");
ziggeo = new Ziggeo(APP_TOKEN, CameraFullscreenRecorderActivity.this);
RecorderConfig config = new RecorderConfig.Builder()
.callback(prepareCallback())
.sendImmediately(true)
.startDelay(3)
.enableCoverShot(false)
.autostartRecording(true)
.disableCameraSwitch(true)
.maxDuration(50000)
.extraArgs(extras)
.quality(CameraView.QUALITY_MEDIUM)
.confirmStopRecording(true)
.facing(CameraView.FACING_FRONT)
.build();
ziggeo.setRecorderConfig(config);
ziggeo.startCameraRecorder(); |
Hi @sagrawal31, |
Thank you, @3akat Since yesterday, we were happy that today we'll finally be able to roll out our app to production track on Google Play but after upgrading SDK to Requesting to pick this issue as soon as you can. Thanks again! |
By the way, I figured out the option (by commenting out the options one by one) which is causing this crash. It's because |
Please take a look at |
😮 I can't believe that you went extra mile to resolve this issue even you were busy. And the biggest thing is that it fixes the issue. Thanks a lot @3akat Hats off to the Ziggeo team! 👍 👍 |
This exception is being thrown very frequently but can be reproduced. This is being thrown when stopped manually or when the timer finishes or when manually stopped (using the checkmark button):
Options I'm using are:
The text was updated successfully, but these errors were encountered: