Closed GoogleCodeExporter closed 9 years ago
Getting the same issue on Gingerbread, 2.3.4, 2.3.5 and 2.3.7 with Locale 2.0
and higher. SL4A Release 4. Python 2.6.
Device: Atrix 4g
OS: Stock 2.3.4 ATT, and on CM7.1 ATRIX 4G B~N release (GB 2.3.5,2.3.7)
Plugin used with: Tasker, Locale.
Basically running any Script called outside of SL4A main screen crashes the
SL4A process.
My assumption is that SL4A and Google's are not referring to the same path when
calling the script.
Similar issues: Please refer to issue: 315 in the issue List.
http://code.google.com/p/android-scripting/issues/detail?id=315&can=1&q=ASE%20fo
rce%20close&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%
20Stars
Logcat attached.
Original comment by jamil.masarweh
on 4 Nov 2011 at 2:15
Attachments:
This is a bug in SL4A, as it isn't properly implementing the Locale 1.0/2.0
API. (SL4A is implementing the Locale 0.5 beta API which was deprecated 2
years ago).
Locale has an advanced configuration control mechanism, which has allowed us to
remotely push out a configuration file to temporarily fix this issue for Locale
users. Within 24 hours, it will no longer be possible
to reproduce this error. But this is only a temporary solution and SL4A ultimately needs a code change to resolve this issue.
The change needs to be made in LocaleReceiver.java. Specifically, this line:
String scriptName = intent.getStringExtra(Constants.EXTRA_SCRIPT_NAME);
needs to be changed to:
String scriptName =
intent.getBundleExtra(com.twofortyfouram.locale.Intent.EXTRA_BUNDLE).getString(C
onstants.EXTRA_SCRIPT_NAME));
The difference is that the plug-in extras are sub-bundled inside EXTRA_BUNDLE.
This change will be compatible with Locale 1.0, Locale 2.0, as well as other
hosts of the Locale Developer Platform.
While this change is being made, I would recommend bringing this
BroadcastReceiver up to date with the latest Locale plug-in examples at
<http://www.twofortyfouram.com/developer.html>. There are a number of security
flaws in SL4A's LocaleReceiver.java, and looking at our examples would be the
easiest way to fix them. For example, the SL4A receiver is susceptible to this
<http://code.google.com/p/android/issues/detail?id=16006>.
Original comment by supp...@twofortyfouram.com
on 9 Nov 2011 at 6:17
Great work by the Locale folks, but we still have a bug, and apparently a
security issue here as well.
Original comment by margaret...@gmail.com
on 9 Nov 2011 at 6:42
Locale folks,
Thank you so much for your assistance on this. I confirm the temporary fix
works! Awesome.
Original comment by jamil.masarweh
on 10 Nov 2011 at 3:37
It would be really great if we could get somebody with committer access to pick
up this one-line change...low hanging fruit here.
Original comment by margaret...@gmail.com
on 10 Nov 2011 at 4:02
Updated Locale committed in sl4aR5x02
Original comment by rjmatthews62
on 19 Nov 2011 at 3:50
Original issue reported on code.google.com by
margaret...@gmail.com
on 4 Nov 2011 at 11:16