x/mobile: app crashed, android 2.3.6 #13172
wasn't aware of ndk constraint on api-15. As mentioned on #13109 I believe the appropriate thing to do is abort on compilation if a manifest declares a minimum api level. The gomobile cmd should then insert the min api tag itself to whatever is decided (+2 to api-15). These are the tentative plans in the issue I linked, but it may be a month or two before that issue is actually resolved.
In the interim, there's little reason the current implementation couldn't go ahead and do this now. This would result in the following behavior as related to the reported issue.
I can put together a CL this weekend if this sounds ok.
In this particular case (the basic example), the manifest file is the default one filled by gomobile tool.
In case a custom manifest file is given, yes, I think it's okay to abort and output helpful error message.
Assigning to @dskinner. Thanks!