Crash on creating state machine builder on Android about squirrel HOT 6 CLOSED

👍 I like the philosophy of not creating that you don't need.

from squirrel.

Hi agrusha,

thanks for let me knowing about this problem.

I am not familiar with android, so I am not quite understand how Android would revive. Because ManagementService is still missing the java.lang.management package even I make instantiate StateMachineBuilder without involving java.lang.management package.

It would be helpful if you can give me more information about this. And also it would be great if you can provide a pull request.

from squirrel.

Well... The actual crash appears to happen only at the moment when android tries to create the instance of ManagementService. As far as it is initiated during StateMachineBuilderImpl creation process it is inevitable that Android bumps into it and throws an exception. But if one makes the way not to initiate the ManagementService object if there is no need in it, then Android won't fall.
Actually I'm working on such sort of solution by myself. I'll let You know if I'd succeed in that.

from squirrel.

Great, thanks!
But my understanding is that ManagementService will cause compile failure as it import javax.management.* which is missing in Android. And defer initiate ManagementService won't help. Is that true? If not, how you solved this problem?

from squirrel.

No, importing does not lead to crash, only trying to use unsupported classes directly

from squirrel.

It looks like it was resolved in 8074cec, I tried 0.3.4 release with this fix cherry-picked and it works for me.

from squirrel.