This issue is fixed in 8.4, but I have the problem in 8.3. I do not know where the root cause of this issue, I just update the route name to fix it.
Any further fix is welcomed.
| Comment | File | Size | Author |
|---|---|---|---|
| routing-name-update.patch | 471 bytes | guaneagler |
Comments
Comment #2
phenaproximaComment #3
phenaproximaI believe this is fixed in Lightning API's latest version for both the 3.x and 4.x versions. If you run a
composer updatein your project to update to the latest version of everything, does this still happen?