ampoz <[email protected]> writes: > Is there a way to disable the MessagingSmsManager? I have a fragment > with an XWalkView and every time I am on that screen and I receive an > SMS, I get the following exception: > > 10-09 15:03:03.648 27389-27389/W/dalvikvm﹕ threadid=1: thread exiting > with uncaught exception (group=0x42033a08) > 10-09 15:03:03.808 27389-27389/E/[PPLCONNECT]﹕ Error receiving > broadcast Intent { act=SMS_SENT flg=0x10 (has extras) } in > org.xwalk.core.internal.extension.api.messaging.MessagingSmsManager$2@4290b398 > 10-09 15:03:03.813 27389-27389/W/System.err﹕ > java.lang.RuntimeException: Error receiving broadcast Intent { > act=SMS_SENT flg=0x10 (has extras) } in > org.xwalk.core.internal.extension.api.messaging.MessagingSmsManager$2@4290b398
https://github.com/crosswalk-project/crosswalk/pull/2456 has recently fixed a bug with a backtrace similar to yours (https://crosswalk-project.org/jira/browse/XWALK-2614), but has not been backported to Crosswalk 9 yet. Can you check if you have the same issue with the 10.38.222.0 canary? If you do, can you please file a bug in JIRA? > I am using v9.38.208.3 from the android maven repo at download.01.org. > (On that note; do you plan on having the latest stable version on the > maven repo anytime soon?) The work on Maven is being tracked in XWALK-1930, and is pretty much done. The idea is to have betas and stables starting with Crosswalk 9 there (there are Crosswalk 10 canaries there at the moment because the work is still being finished). _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
