Will this actually compile with the import to the platform Activity extension, or is it a tooling error?

we are pushing people towards ComponentActivity since we are able to leverage lifecycles to handle things properly like state restoration, releasing references on stop, etc.

but AppCompatActivity is extending ComponentActivity so this error shouldn't be displayed as we use the proper overload, interesting

Yes, I'm extending AppCompatActivity

anyway, we will soon remove this deprecated overload and it will only compile inside AppCompatActivity or ComponentActivity

OK, thanks!

oh whoops. missed that