Closed mooocer closed 6 years ago
It should display the bottom sheet view with attendee detail and control to checkin or checkout the attendee
@iamareebjamal For checking small number of attendees, organizers can directly use the bottom sheet view by clicking the list items with search. Scanning, I think, is generally used for a queue of attendees. In that case if we repeatedly close the camera and make the organizer check-in/out the attendees manually, it would be cumbersome IMO. And that's why scan settings were added to decide what scanning does, just like in EventBrite.
Camera and Fragment closing is a bug, it never closed. The current flow was
Scan QR code -> Bottom Sheet Appears -> You check in or check out the attendee -> Scanning Resumes
But shouldn't the middle 2 steps (Bottom Sheet Appears -> You check in or check out the attendee) be removed as it'll already be defined what scanning has to do? Or we can do as per scan settings, but still show the bottom sheet, so that organizer might reverse the step if it was not intended?
Yes, there should be 3rd setting, show checkin status which shows the bottom sheet
This bug was giving different stack traces in both devices, and shows the error No injector was found for org.fossasia.openevent.app.core.attendee.checkin.AttendeeCheckInFragment
for the device with API 24, and irrelevant warning for the other one.
This : https://github.com/mishuvs/open-event-orga-app/commit/e431fe8a7e33cd0fd85a0c60570cf3914d7ea9b8 is what I am trying to do, which is giving me the build errors:
error: @Subcomponent.Builder is missing setters for required modules or subcomponents: [org.fossasia.openevent.app.common.di.module.BarcodeModule]
error: org.fossasia.openevent.app.common.di.module.android.ActivityBuildersModule_ContributeScanQRActivity.ScanQRActivitySubcomponent (unscoped) may not reference scoped bindings:
@Provides @Singleton @Named("barcodeEmitter") io.reactivex.subjects.PublishSubject<io.reactivex.Notification<com.google.android.gms.vision.barcode.Barcode>> org.fossasia.openevent.app.common.di.module.BarcodeModule.providesBarcodeEmitter()
First one is probably because of BarcodeModule
not having parameter-less constructor:
public BarcodeModule(GraphicOverlay<BarcodeGraphic> graphicOverlay) {
this.graphicOverlay = graphicOverlay;
}
But I am not able to make it parameter-less.
@iamareebjamal @srv-twry @Masquerade0097 is there an alternate we can follow?
This may be due to the new AndroidInjector change I made
Check that out
Yes, you are right. It was after adding AndroidInjector that it started crashing. I am not able to figure it out yet, but I think it should be a small fix. What do you suggest I should do now?
Rather than using AndroidInjector, use the old approach in this particular fragment
Is it a ?
Bug Report
Actual Behaviour
When an attendee is scanned, the camera stops and attendee fragment closes without checking in or checking out the attendee.
Expected Behaviour
After scanning, an attendee should be checked in or out.
Steps to reproduce it
LogCat for the issue on Xiaomi Redmi 4A
LogCat for the issue on Samsung SM-G615F (API 24)
GIF of the issue
Android version and Phone Model
6.0.1 - Xiaomi Redmi 4A
Would you like to work on the issue?
Yes