Constraint layout Layout Crashing : All Children of constraint layout should have ids to use constraint set

Question

After updating to com.android.support.constraint:constraint-layout:1.1.0

The constraint layout crashes saying:

All children of constraint layout should have ids to use constraint set

I have set ids to all views even then it's crashing.

java.lang.RuntimeException: All children of ConstraintLayout must have ids to use ConstraintSet at android.support.constraint.ConstraintSet.clone(ConstraintSet.java:687) at com.zoho.notebook.views.SettingsViewNavBar.showNoteSettingsView(SettingsViewNavBar.java:594) at com.zoho.notebook.views.SettingsViewNavBar.onClick(SettingsViewNavBar.java:303)

Do you mind sharing a [mvce](https://stackoverflow.com/help/mcve)? — leonardkraemer, May 25 '18 at 10:20
please, put your layout and the way you are using constraintSet, otherwise is hard to give you a solution to your problem. — Leandro Ocampo, May 25 '18 at 10:24

hushed_voice · Accepted Answer · 2018-06-24T08:43:17.147

50

I had the same bug in my code. I had ids for all the views in xml, but I was manually adding a view to the constraint layout(a Tooltip view) with

constraintParent.addView(childView)

and while the dynamically added view is still on the parent if the constraint layout is redrawn (app goes to bg and resumed) this exception was getting triggered.

I fixed it by generating a view id for the dynamic view like this

CustomViewChildView childView = new CustomViewChildView()
childView.setId(View.generateViewId());

and then adding it to the constraint layout.

edited Jun 24 '18 at 08:43

answered Jun 15 '18 at 06:41

hushed_voice

3,161
3
34
66

1

not works for me, I'm not adding views dynamically and all child views had ids, but steel crashes with same error – Jemo Mgebrishvili Jan 16 '19 at 13:19
1

@JemoMgebrishvili Please double check your code. When ever I faced the error, it was either missing id in xml or while dynamically adding view(which could be invisible) – hushed_voice Jan 17 '19 at 08:34
Just to clarify that you should use: `nameOfChildView.setId(View.generateViewId());` where you replace "nameOfChildView" with your "ChildView's" variable name. – Ola Ström Jan 23 '22 at 15:14

Onderbetaald · Answer 2 · 2019-04-12T14:04:24.800

17

Don't forget to give the ConstraintLayout an id as well.

I forgot this and it crashed my code. This isn't really obvious from the error.

edited Apr 12 '19 at 14:04

answered Mar 22 '19 at 19:46

Onderbetaald

321
2
9

You made my day! – Giacomo Santarnecchi Mar 11 '20 at 16:15

score 5 · Answer 3 · answered Oct 03 '18 at 04:38

I just figure out how to fix this problem. Notice that is you must declare all view on ConstrainLayout have set ids, check example below:

In case 1 it's working success.

<android.support.constraint.ConstraintLayout 
    android:id="@+id/viewGroup"
    ...>
    <ImageView
        android:id="@+id/imgId"
        ... />
    <TextView
        android:id="@+id/txtId"
        ... />

In case 2 below not working.

<android.support.constraint.ConstraintLayout 
        android:id="@+id/viewGroup"
        ...>
        <ImageView
            android:id="@+id/imgId"
            ... />
        <TextView
          // do not set ids
            ... />

I hope this it will helpful for you.

score 2 · Answer 4 · answered Jul 07 '20 at 14:43

2

I was getting this error until I realized that I hadn't given ids to some of the child elements in the ConstraintLayout. So, make sure you do not forget to do that either.

answered Jul 07 '20 at 14:43

sayleep

19
5

score 0 · Answer 5 · answered Jul 09 '21 at 07:58

0

In my case Don't forget to add ID to all child of contraintLayout

answered Jul 09 '21 at 07:58

rizkidzulkarnain

61
1
12

score 0 · Answer 6 · edited Aug 07 '21 at 20:04

I had this error when I tried to add new View at onGlobalLayout() (after main Layout is finalized). All id's in Layout were correct, new dynamical View ID was set (with setId()). But fault "All Children of constraint layout should have ids to use constraint set" kept occuring.

When I moved adding View to onCreate() everything went smooth. I just needed to change logic however on how where to put new View, as position of other Views is not determined at onCreate().

score 0 · Answer 7 · edited Aug 04 '23 at 16:55

0

In my case, the crash appeared after I used the Refactor -> Remove Unused Resources feature. This action deleted an ID from the MotionScene layout description, and the same ID was also removed from the corresponding MotionLayout.

edited Aug 04 '23 at 16:55

Megh

831
2
12

answered Jul 27 '23 at 09:53

Roman Markov

3
2

Constraint layout Layout Crashing : All Children of constraint layout should have ids to use constraint set

7 Answers7