Crash: onMeasure() did not set the measured dimension by calling setMeasuredDimension() about falcon

[jraska]

Hello, thanks for using Falcon.

This looks weird and I guess its annoying, but I don't think Falcon directly causes this, I believe Falcon crash is just a symptom of other problem.

Briefly looking online this exception is not new and was experienced by many people. What I can guess it is a race condition when Falcon takes the screenshot, but there could be many causes.

Could you please provide test case reproducing the crash? Without that there is very little I can do.

[zeeshanalisayyed]

Hi,

Thank you!

There is no pattern or test case I ever found to reproduce the crash, but it mostly happens when I swipe (up|down|left|right) and tap faster to navigate through items in the lists and tabs. While testing, I am hardly able to reproduce it doing the fast interaction but in live I can see many crashes related to this particular crash on crashlytics, and when I remove falcon, this crash does not occur.

As mentioned, you can try to reproduce the crash on any app which has list of items in a list view and tabs which can be swipe-able in all directions and list item has some images and texts which are being loaded from the internet at runtime, and you can try few fast sessions:

FrameLayout, CoordinatorLayout, RelativeLayout, TabLayout, android.support.v4.widget.NestedScrollView, AppBarLayout, Custom Views, CoordinatorLayout, etc.

[jraska]

Hello again,

I think this is more likely a problem within Android layouts, which is indirectly triggered by Falcon, because in the end everything Falcon does is calling View.draw(Canvas canvas). While looking at this method docs you can find the following:

...
* The view must have already done a full layout before this function is
* called.
...

By searching I found several people having this issue in different situations and my guess is you try to do screenshot too early within layout creation and since it happens rarely my thoughts go to concurrency issue.
One of the ideas would be to ensure activity is resumed before taking screenshot, but this goes beyond responsibilities of Falcon so I would recommend trying it by yourself.

However this is just a guess and I cannot confirm this without runnable test, which will at least sometimes fail. Therefore no-fix so far unfortunately.

[Android355]

@zeeshanalisayyed Hi, did you manage to solve this problem?