Consider adding some javax.swing classes and interfaces to the JVM White List [35884128]

Assigned

Feature Request

Status Update

No update yet.

Description

jo...@gmail.com

created issue #1

Apr 15, 2009 04:28PM

When trying an ItsNat web application in Google App Engine it throws:

java.lang.NoClassDefFoundError: javax.swing.event.EventListenerList is a
restricted class. Please see the Google App Engine developer's guide for
more details.

ItsNat reuses some Swing classes and interfaces (EventListenerList is an
example) in a web environment.

Swing classes like data models and selection models
(javax.swing.ListModel,javax.swing.tree.TreeModel,
javax.swing.ListSelectionModel, javax.swing.TreeSelectionModel,
java.util.EventObject, javax.swing.CellEditor,
javax.swing.AbstractCellEditor etc) have no screen relationships, in fact,
they were designed to be UI independent.

I think there is no security concern with Swing classes in a screen-less
environment like GAE. Why can't the full Swing stack be included into the
JVM white list?

ItsNat is not the first using these classes, for instance Wicket uses tree
model and listeners, wingS or Echo make intensive use of these classes too.

If you need a complete list of public UI independent classes and interfaces
of Swing used by ItsNat, contact with me if you want.

Jose M. Arranz

Comments

jo...@gmail.com <jo...@gmail.com> #2Apr 16, 2009 07:09AM

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

to...@google.com <to...@google.com> #3Apr 23, 2009 07:11PM

Assigned to to...@google.com.

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

jo...@gmail.com <jo...@gmail.com> #4Apr 23, 2009 08:14PM

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

jo...@gmail.com <jo...@gmail.com> #5Apr 24, 2009 04:19PM

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

jo...@gmail.com <jo...@gmail.com> #6Apr 24, 2009 04:31PM

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

jo...@gmail.com <jo...@gmail.com> #7Apr 24, 2009 04:33PM

Note that I've been able to make it work by:

Adding <action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> in the intent filter
Removing <data android:scheme="wear" android:host="*" />

But I feel like this is not something we should do

ha...@gmail.com <ha...@gmail.com> #8May 7, 2009 03:00AM

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

th...@googlemail.com <th...@googlemail.com> #9May 7, 2009 03:51AM

If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.

But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.

th...@googlemail.com <th...@googlemail.com> #10May 7, 2009 04:39AM

As an interim update on this issue: we've been already working on the fix that should be available by Android 13 release. The fix requires thorough testing, I'll keep this bug updated as soon as we have more to share. Thanks!

an...@stroet.org <an...@stroet.org> #11May 18, 2009 08:16PM

@comment#9 The Play Store will eventually require targeting API 33, then 34, etc, so accepting this regression in a customer release would be a time ticking bomb for Wear OS apps.

Thank you for the update @comment#10

go...@gmail.com <go...@gmail.com> #12May 19, 2009 10:17PM

Hey @

comment#10

, do you have any news to share?

Android 13 is out today and we still have no patch unlike what you said a month ago

al...@gmail.com <al...@gmail.com> #13Oct 27, 2009 01:52PM

I have no words for this. Android 13 is labeled "stable" but the Wearable API just doesn't work. Can't this issue be given higher priority? If you want to push WearOS you need to make sure it works normally.

sh...@gmail.com <sh...@gmail.com> #14Oct 28, 2009 08:24AM

This issues has been already given high priority (updated external priority on this bug to reflect internal status). The fix is on the way and going through the final rounds of testing, so the roll out is slated to next couple of weeks.

To reiterate what have been mentioned earlier on this bug: this issue affects only apps targeting Android 13, so the apps won't break unless you bump targetSDK version to 33. In case if you want to start working on app compatibility for Android 13 behaviour changes, you could use Compatibility framework to toggle on/off the changes individually for isolated testing.

ig...@gtempaccount.com <ig...@gtempaccount.com> #15Dec 14, 2009 09:20AM

comment#14

as much as I agree that is not a blocking bug, you need to understand that:
- The report is 2 months old
- Google chose to release Android 13 with that bug
- There's no mention of this bug on the documentation so you can totally bump your targetSdk without noticing it

So thank you guys for working on this but it's still not a valid excuse for taking that long for such an important issue. Now that being said, let us know when a fix is available

sh...@gmail.com <sh...@gmail.com> #16Dec 16, 2009 07:49PM

Google will come through. They always do!

al...@gmail.com <al...@gmail.com> #17Feb 22, 2010 12:33AM

That must be some really intense testing as we are 10 days later and still nothing on sight. I don't want to be a P2 issue if that's what a P1 is.

sh...@gmail.com <sh...@gmail.com> #18May 25, 2010 05:04PM

Is there an update on by when can we expect a fix for this? We are blocked on the app release which is targeting Android 13. We can't roll out if it doesn't support wear os app.

ja...@googlemail.com <ja...@googlemail.com> #19Sep 15, 2010 08:26AM

@Google Any updates here?

q3...@gmail.com <q3...@gmail.com> #20May 24, 2011 11:28AM

I have to imagine this needs to be fixed, at least, for the launch of the Pixel Watch.

pr...@google.com <pr...@google.com> #21Aug 27, 2011 12:49AM

My bet is that Google still targets API 32 (or even lower) internally so they don't care and didn't even saw the issue before our report.