Activated hook is not triggering when mounting childs of an async component

[dbssman]

Vue version

3.2.45

Link to minimal reproduction

https://sfc.vuejs.org/#eNrVVMFymzAQ/ZUdDok9MRCnNxd76sm943vIgcDaVgwSIwmaDsO/d4VAYCfjSXpqL4jV7nuSnvap8bZlGdQVeisvUqlkpQaFuio3MQdgRSmkhkdRlLCXooDbIDSBAdxOCnaJRK5diQ0vi5oM94zjVv3mqSERnIoWEveLlKJKY9b2DAMwFVxp+va1CtbwBCYB8BHXbDZfb2BHFExhIFGJvMaZSc/ni6/C7Bnmc4N7/m6+445YRjuhjc/uu3S/zUpKx0n54VBED8Q/nuKJZUGd5BU+d+iRoZRYE9DWD0WwgXu4uXGx748Ajm9mpQtANFkryJEf9NFfTinu7mIehfay6Zop0FiUeaKxu/TouNxsU81qmsjgKMQJBAd9REiPLM8UiD0kHBIj4rhUFBLMwh82j6SFUcFlgfEM36BpWNa2VPpgS0+IpZ/krLYrxzoaESum1rF3pmrsbaLQVViK8IIjeqm0pv3+SHOWnojBqErAHQ1RaJMfFxo1qfAnDZPCKHTieAvPtrJfJGXwqgQn0zTdxvuEir0VdDNmjtrYxLF31LpUqzBU+9SY4lUFQh5C+gtkxTUrMEBV+C9S/FIoiTj2+nbtOEKarFH6pGiGEuU1zovSd7yGto15S0cZfHzN+I3grhOMUy8NOjUpnQSl84VzzITBGq2Xpwf0HbledgDLJnIMcnGY3Y5d6B6dzjItfa828LduBAeDxDE1Tb9y24KRXtku6iDndz2+YlffRuOJ8XE00buH719RcfIuf0pHhQQd7OJEHVk+KSv9dLqQee1ocwO7OeG58k7F/6M33Z1/sTkH3F90Z/sHxaahZA==

Steps to reproduce

• Enter the playground
• Use the buttons to navigate between async components

What is expected?

Child.vue being a child component of Parent.vue would trigger onActivated hook when mounted. following the docs: https://vuejs.org/guide/built-ins/keep-alive.html#lifecycle-of-cached-instance

What is actually happening?

Child component starts triggering onActivated after the initial mount

System Info

No response

Any additional comments?

No response

[yxchai]

@dbssman Is this resolved on your side? Is there a temp workaround for this? Thanks.

I noticed there's a PR waiting approval. Is there anyone can look into it? @zhangzhonghe Any luck with getting the PR reviewed and released? Thanks.

I'm experiencing the same thing. And I can recreated this bug in SFC Playground too.

In my playground, the first time you open it, the child component inside the async comp is mounted but never triggering the activated hook. That's the first time the async comp is loaded. But if you click on the toggle button, I can see the child component inside the async comp is triggering activated.

[zhangzhonghe]

Any luck with getting the PR reviewed and released? Thanks.

@yxchai You could leave a comment in #7286 and @yyx990803 to review it. Maybe it will get yyx's attention.

[dbssman]

@dbssman Is this resolved on your side? Is there a temp workaround for this? Thanks.

@yxchai I have a workaround but very specific to my project and that might not work for you, or not be what you need, If you're still interested in it lemme know.

[yxchai]

@yxchai I have a workaround but very specific to my project and that might not work for you, or not be what you need, If you're still interested in it lemme know.

Thanks for the reply, @dbssman, I was able to work out a way in my project specifically. So, all good here.

[719media]

This bug affected me unexpectedly today. I assume bandwidth just isn't there to get this reviewed and pushed. Just commenting to keep this thread alive!