objectivetruth / uoitdclibrarybooking Goto Github PK

Expected Behavior:

Shows the correct day of the week

Current Behavior:

Shows 2 days behind the current date. The 27th is a Saturday, not a Thursday

in okhttp3.Dns$1.lookup

• Number of crashes: 1
• Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/wwwobjectivetruthca/android/apps/com.objectivetruth.uoitlibrarybooking/issues/599303acbe077a4dcc1e5552?utm_medium=service_hooks-github&utm_source=issue_impact

Like the old app but with Material design and Dependency Injection

in com.objectivetruth.uoitlibrarybooking.userinterface.calendar.grid.Grid.onCreateView

• Number of crashes: 1
• Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/wwwobjectivetruthca/android/apps/com.objectivetruth.uoitlibrarybooking/issues/57cc3e860aeb16625bb20594

To reproduce:
Pull to refresh, and while its refreshing, quickly switch to another screen. When the refresh finishes, it will overlay overthe current screen and won't go away until you go back to the calendar screen

Should only do the refresh if the user scrolls to the very top of the calendar

For unit testing purposes

in some_crashed_method

• Number of crashes: 0
• Impacted devices: 0

There's a lot more information about this crash on crashlytics.com:
http://example.com/path/to/fabric/issue

Like the old app but with Material Design and Dependency Injection

Occurs on non-closed days and at non-closed times before 10am

Dear developers,
I am developing a tool to detect hang-bugs of android apps. A hang-bug happens when the execution of heavy APIs on the main thread lead the main thread to be unresponsive for an amount of time longer than the human-eye perceivable delay. We tested the master version of your app and found that the usage of the following Timber library API:

timber.log.Timber.v

timber.log.Timber.i

cause hang-bugs with the user perceiving a freeze of almost 1 second. We detect this hang-bug specially when the app is opened but also in other interactions with the app. In particular, an extract of stack trace that calls the above API is the following:

1)com.objectivetruth.uoitlibrarybooking.Calendar_Generic_Page_Fragment.onCreateView(Calendar_Generic_Page_Fragment.java:114)

2)com.objectivetruth.uoitlibrarybooking.Calendar_Generic_Page_Fragment$CalendarAdapter.<init>(Calendar_Generic_Page_Fragment.java:293)

3)timber.log.Timber.v(Timber.java:13)

Moving heavy tasks off the main thread helps improving the responsiveness of the app. Therefore, we think that moving off the main thread (e.g., using AsyncTask for example) the execution of the Timber library APIs (Timber.i, Timber.v) in the CalendarAdapter method would fix this hang-bug and greatly help improving the responsiveness of your app.

Do you think that this approach would help improving the responsiveness of the app?

Thanks a lot for any reply,
Hope to help improving UoitDCLibraryBooking's responsiveness

Due to this line

https://github.com/ObjectiveTruth/UoitDCLibraryBooking/blob/master/app/build.gradle#L17

        classpath 'com.android.tools.build:gradle:2.2.0-beta1'

Redo the app in the new Material style and with Dependency Injection

Perhaps the roadrunner style loading screen?

https://github.com/glomadrian/RoadRunner

*Intended Behavior *

No Ads

Current Behavior

Ads and paywalls everywhere

in com.objectivetruth.uoitlibrarybooking.userinterface.calendar.common.CalendarPagerAdapter._getDayOfWeekFromCalendarDataAtPosition

• Number of crashes: 1
• Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/wwwobjectivetruthca/android/apps/com.objectivetruth.uoitlibrarybooking/issues/57ed7cd60aeb16625beaef8b

in com.objectivetruth.uoitlibrarybooking.userinterface.myaccount.myaccountloaded.BookingsAdapter.

• Number of crashes: 1
• Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/wwwobjectivetruthca/android/apps/com.objectivetruth.uoitlibrarybooking/issues/583c3c910aeb16625b5f91d2

in com.objectivetruth.uoitlibrarybooking.data.models.usermodel.UserWebService._getRawInitialSignInWebpage

• Number of crashes: 1
• Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/wwwobjectivetruthca/android/apps/com.objectivetruth.uoitlibrarybooking/issues/5972c009be077a4dccf0becb?utm_medium=service_hooks-github&utm_source=issue_impact

in android.os.BinderProxy.transactNative

• Number of crashes: 1
• Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/wwwobjectivetruthca/android/apps/com.objectivetruth.uoitlibrarybooking/issues/58e28af50aeb16625b32f5ac

Intended Behaviour
Pressing a menu item changes the current screen to the selected screen

Current Behaviour:
Pressing a menu item closes the drawer and stays on the same screen

in com.objectivetruth.uoitlibrarybooking.userinterface.myaccount.myaccountloaded.BookingsAdapter.

• Number of crashes: 1
• Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/wwwobjectivetruthca/android/apps/com.objectivetruth.uoitlibrarybooking/issues/57cf3a900aeb16625bd0c84e

Something to do with the task ./gradlew bootstrapReleasePlayResources

Linked to the use of the avd software emulator.

Found here

https://github.com/ObjectiveTruth/UoitDCLibraryBooking/blob/beta/circle.yml#L17-L19

test:
  override:
    # Run unit tests first (results will be collected at the last step)
    - ./gradlew test -PdisablePreDex
    # start the emulator
    - emulator -avd circleci-android22 -no-audio -no-window:
        background: true
        parallel: true
    # wait for it to have booted
    - circle-android wait-for-boot
    # unlock the emulator screen
    - sleep 30
    - adb shell input keyevent 82