All three floating action buttons have retained the default hero tags within the same subtree which might throw errors during navigation as such.
ââââââââ Exception caught by scheduler library âââââââââââââââââââââââââââââââââ
The following assertion was thrown during a scheduler callback:
There are multiple heroes that share the same tag within a subtree.
Within each subtree for which heroes are to be animated (i.e. a PageRoute subtree), each Hero must have a unique non-null tag.
In this case, multiple heroes had the following tag:
Here is the subtree for one of the offending heroes: Hero
tag:
state: _HeroState#45464
When the exception was thrown, this was the stack
#0 Hero._allHeroesFor.inviteHero.
package:flutter/âĻ/widgets/heroes.dart:268
#1 Hero._allHeroesFor.inviteHero
package:flutter/âĻ/widgets/heroes.dart:279
#2 Hero._allHeroesFor.visitor
package:flutter/âĻ/widgets/heroes.dart:298
#3 SingleChildRenderObjectElement.visitChildren
package:flutter/âĻ/widgets/framework.dart:6105
#4 Hero._allHeroesFor.visitor
It might be useful to specify distinct heroTag:
values for each. Also a simple UX addition such as rotating or transforming the main fab from a +
to a x
when active might serve you well.