Great news. Sadly my journey to 10x has hit a snag…
I had a whole bunch of issues with different/more strict behaviour in the compiler w.r.t visiblity of classes. Mostly to do with nested classes not being explicitly public when they needed to be and a seemingly more strict behaviour w.r.t handling collisions between a nested type name and a class member with the same name:
Foo = public class
Public property Bar := new Foo.Bar;
End;
Bar nested in Foo = public class
End;
In 9.x this was fine… the compiler seemed happy to be able to resolve the difference between a reference to instance.Bar and type.Bar. But 10.x choked. A minor refactoring to provide discriminating names so no big deal, but the actual names in question made this a bit irksome (the names for the nested class and the property refering to an instance of that nested class were both most natural in their previous, common form so the fact that compiler had become more fussy than before was annoying, but not a showstopper).
However after dealing with these issues I then ran into a Null Object Reference error from the compiler. So I reverted to 9.x to a) check that my changes were still 9.x “compatible”, just in case, and b) to make sure that the NOR problem was not endemic to the project/solution as a result of those changes.
This dealt with the NOR error (I was once again able to compile) but I have been struggling for a while with a debugging behaviour problem. In an attempt to resolve that I updated my Android SDK build/platform tools which not only has not fixed my debugging problem but also completely broke my Google Sign In implementation.
This has now become my top priority for this project so the 10.x transition has gone back on hold. 
Incidentally, the debugging problem is weird: The app builds, deploys on the device (physical, not emu) and launches but then get’s stuck. I have a splash activity which launches my main activity but the debugger freezes (not a breakpoint - there is no “continue” option) before the main activity onCreate completes. Timber logging shows that the onCreate is entered.
I hit STOP in Visual Studio and the app then conntinues normally. I.e. the application instance launched from within VS/debugger is not itself terminated by the STOP, but the debugger session is ended, with the application then continuing to run normally. There are no errors in the adb logcat output.
If I launch the app on the device normally, it goes straight through the splash, into the main activity, with no problems.
This seems something specific to my app because a hello world Android project doesn’t have any similar problem, but I’m at a loss what might cause such behaviour. Any ideas ?
