Phonegap app rejected on Amazon Marketplace

456 views
Skip to first unread message

Math-on-Phone

unread,
Jan 31, 2011, 11:41:23 PM1/31/11
to phonegap
Hi Everyone,

My relatively simple "Math-a-Mole" app has been rejected from Amazon
Marketplace. I believe it is related to the "javascript bridge" issue
also known as the "Gingerbread 2.3 emulator" issue. I have reason to
believe the problem is more widespread and affects real hardware too.

Here are the exact words from the Amazon testing team:

"- App fails to launch successfully on Droid Incredible 2.2. When
launched, a message appears (to quick to read) and then phone's screen
goes black. No other message or image appears."

Interesting eh? They say 2.2 there but the "popular" consensus is that
this only happens in 2.3 emulator and not even on a 2.3 phone.

Here in the phonegap lighthouse app we say this issue is "invalid"
since it is a breakage on Google's side:

http://phonegap.lighthouseapp.com/projects/20118/tickets/61-sample-app-does-not-run-on-23

Here in a google issue tracker people say that another 2.2 os ZTE
Blade has the issue:

http://code.google.com/p/android/issues/detail?id=12987

Me personally I found the following in testing:
1) Samsung Behold II (real phone) - 1.5 cupcake os - works
2) 1.5 cupcake emulator - works
3) 2.2 emulator - works
4) 2.3.1 emulator - fails!

To summarize the javascript bridge issue is affected in one emulator
and at least two real phones:
1) 2.3.x emulator - fails
2) Droid Incredible 2.2 - fails
3) ZTE Blade 2.2 - fails

I realize this is probably not something *we* can do but do any of you
have any pull with those at google creating these api kits? This seems
like a serious issue that can prevent us from deploying our apps on
new Android devices.

Cheers,
-- Aaron

The following is my log trace from the 2.3.1 emulator:

01-31 23:07:09.311: DEBUG/AndroidRuntime(585): >>>>>> AndroidRuntime
START com.android.internal.os.RuntimeInit <<<<<<
01-31 23:07:09.311: DEBUG/AndroidRuntime(585): CheckJNI is ON
01-31 23:07:10.231: DEBUG/AndroidRuntime(585): Calling main entry
com.android.commands.pm.Pm
01-31 23:07:10.281: DEBUG/AndroidRuntime(585): Shutting down VM
01-31 23:07:10.301: DEBUG/dalvikvm(585): GC_CONCURRENT freed 102K, 71%
free 297K/1024K, external 0K/0K, paused 2ms+1ms
01-31 23:07:10.311: INFO/AndroidRuntime(585): NOTE: attach of thread
'Binder Thread #3' failed
01-31 23:07:10.381: DEBUG/dalvikvm(585): Debugger has detached; object
registry had 1 entries
01-31 23:07:11.040: DEBUG/AndroidRuntime(595): >>>>>> AndroidRuntime
START com.android.internal.os.RuntimeInit <<<<<<
01-31 23:07:11.040: DEBUG/AndroidRuntime(595): CheckJNI is ON
01-31 23:07:11.870: DEBUG/AndroidRuntime(595): Calling main entry
com.android.commands.am.Am
01-31 23:07:11.930: INFO/ActivityManager(76): Force stopping package
com.drrosey.games.dr_rosey_math_mole_ultimate uid=10030
01-31 23:07:11.930: INFO/ActivityManager(76): Starting: Intent
{ act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10000000
cmp=com.drrosey.games.dr_rosey_math_mole_ultimate/.DrRoseyMathMoleUltimate }
from pid 595
01-31 23:07:12.020: INFO/ActivityManager(76): Start proc
com.drrosey.games.dr_rosey_math_mole_ultimate for activity
com.drrosey.games.dr_rosey_math_mole_ultimate/.DrRoseyMathMoleUltimate:
pid=603 uid=10030 gids={3003, 1015}
01-31 23:07:12.030: DEBUG/AndroidRuntime(595): Shutting down VM
01-31 23:07:12.060: DEBUG/dalvikvm(595): GC_CONCURRENT freed 104K, 69%
free 321K/1024K, external 0K/0K, paused 2ms+2ms
01-31 23:07:12.090: INFO/AndroidRuntime(595): NOTE: attach of thread
'Binder Thread #3' failed
01-31 23:07:12.131: DEBUG/jdwp(595): Got wake-up signal, bailing out
of select
01-31 23:07:12.131: DEBUG/dalvikvm(595): Debugger has detached; object
registry had 1 entries
01-31 23:07:12.721: DEBUG/dalvikvm(33): GC_EXPLICIT freed 12K, 53%
free 2531K/5379K, external 1625K/2137K, paused 647ms
01-31 23:07:12.950: DEBUG/dalvikvm(33): GC_EXPLICIT freed <1K, 53%
free 2531K/5379K, external 1625K/2137K, paused 226ms
01-31 23:07:13.060: DEBUG/dalvikvm(33): GC_EXPLICIT freed <1K, 53%
free 2531K/5379K, external 1625K/2137K, paused 94ms
01-31 23:07:13.531: WARN/ActivityThread(603): Application
com.drrosey.games.dr_rosey_math_mole_ultimate is waiting for the
debugger on port 8100...
01-31 23:07:13.591: INFO/System.out(603): Sending WAIT chunk
01-31 23:07:13.641: INFO/dalvikvm(603): Debugger is active
01-31 23:07:13.830: INFO/System.out(603): Debugger has connected
01-31 23:07:13.830: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:14.030: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:14.231: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:14.441: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:14.641: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:14.840: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:15.040: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:15.250: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:15.451: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:15.651: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:15.850: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:16.050: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:16.259: INFO/System.out(603): waiting for debugger to
settle...
01-31 23:07:16.461: INFO/System.out(603): debugger has settled (1405)
01-31 23:07:17.100: INFO/System.out(603): loadUrl(file:///
android_asset/www/index.html)
01-31 23:07:17.110: INFO/System.out(603): url=file:///android_asset/
www/index.html baseUrl=file:///android_asset/www
01-31 23:07:18.401: DEBUG/dalvikvm(603): GC_EXTERNAL_ALLOC freed 74K,
52% free 2626K/5379K, external 1794K/2137K, paused 63ms
01-31 23:07:19.820: INFO/ActivityManager(76): Displayed
com.drrosey.games.dr_rosey_math_mole_ultimate/.DrRoseyMathMoleUltimate:
+7s810ms
01-31 23:07:20.840: DEBUG/szipinf(603): Initializing inflate state
01-31 23:07:20.890: DEBUG/szipinf(603): Initializing zlib to inflate
01-31 23:07:20.954: DEBUG/szipinf(603): Initializing inflate state
01-31 23:07:21.000: DEBUG/szipinf(603): Initializing zlib to inflate
01-31 23:07:21.100: DEBUG/szipinf(603): Initializing inflate state
01-31 23:07:21.180: DEBUG/szipinf(603): Initializing zlib to inflate
01-31 23:07:26.441: DEBUG/dalvikvm(237): GC_EXPLICIT freed <1K, 49%
free 2952K/5767K, external 7693K/9607K, paused 1476ms
01-31 23:07:30.300: WARN/dalvikvm(603): JNI WARNING: jarray 0x405e7900
points to non-array object (Ljava/lang/String;)
01-31 23:07:30.300: INFO/dalvikvm(603): "WebViewCoreThread" prio=5
tid=9 NATIVE
01-31 23:07:30.310: INFO/dalvikvm(603): | group="main" sCount=0
dsCount=0 obj=0x40522768 self=0x2a1af8
01-31 23:07:30.310: INFO/dalvikvm(603): | sysTid=612 nice=0
sched=0/0 cgrp=default handle=2761928
01-31 23:07:30.320: INFO/dalvikvm(603): | schedstat=( 8180619826
4262422418 557 )
01-31 23:07:30.320: INFO/dalvikvm(603): at
android.webkit.BrowserFrame.stringByEvaluatingJavaScriptFromString(Native
Method)
01-31 23:07:30.320: INFO/dalvikvm(603): at
android.webkit.BrowserFrame.stringByEvaluatingJavaScriptFromString(Native
Method)
01-31 23:07:30.340: INFO/dalvikvm(603): at
android.webkit.BrowserFrame.loadUrl(BrowserFrame.java:246)
01-31 23:07:30.340: INFO/dalvikvm(603): at
android.webkit.WebViewCore.loadUrl(WebViewCore.java:1570)
01-31 23:07:30.340: INFO/dalvikvm(603): at
android.webkit.WebViewCore.access$1400(WebViewCore.java:53)
01-31 23:07:30.340: INFO/dalvikvm(603): at android.webkit.WebViewCore
$EventHub$1.handleMessage(WebViewCore.java:956)
01-31 23:07:30.350: INFO/dalvikvm(603): at
android.os.Handler.dispatchMessage(Handler.java:99)
01-31 23:07:30.361: INFO/dalvikvm(603): at
android.os.Looper.loop(Looper.java:123)
01-31 23:07:30.361: INFO/dalvikvm(603): at android.webkit.WebViewCore
$WebCoreThread.run(WebViewCore.java:629)
01-31 23:07:30.361: INFO/dalvikvm(603): at
java.lang.Thread.run(Thread.java:1019)
01-31 23:07:30.371: ERROR/dalvikvm(603): VM aborting
01-31 23:07:30.480: INFO/DEBUG(510): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
01-31 23:07:30.491: INFO/DEBUG(510): Build fingerprint: 'generic/sdk/
generic:2.3.1/GSI11/93351:eng/test-keys'
01-31 23:07:30.491: INFO/DEBUG(510): pid: 603, tid: 612 >>>
com.drrosey.games.dr_rosey_math_mole_ultimate <<<
01-31 23:07:30.491: INFO/DEBUG(510): signal 11 (SIGSEGV), code 1
(SEGV_MAPERR), fault addr deadd00d
01-31 23:07:30.491: INFO/DEBUG(510): r0 fffffebc r1 deadd00d r2
00000026 r3 00000000
01-31 23:07:30.491: INFO/DEBUG(510): r4 81da45c8 r5 405e7900 r6
81d859ec r7 002a2dc0
01-31 23:07:30.491: INFO/DEBUG(510): r8 43f3faf8 r9 43e14e20 10
00000000 fp 41a3e8b8
01-31 23:07:30.520: INFO/DEBUG(510): ip 81da4728 sp 43f3f620 lr
afd19375 pc 81d45a02 cpsr 20000030
01-31 23:07:30.930: INFO/DEBUG(510): #00 pc 00045a02 /
system/lib/libdvm.so
01-31 23:07:30.930: INFO/DEBUG(510): #01 pc 000376fc /
system/lib/libdvm.so
01-31 23:07:30.941: INFO/DEBUG(510): #02 pc 000399c4 /
system/lib/libdvm.so
01-31 23:07:30.941: INFO/DEBUG(510): #03 pc 0003a4a0 /
system/lib/libdvm.so
01-31 23:07:30.951: INFO/DEBUG(510): #04 pc 0032b6e6 /
system/lib/libwebcore.so
01-31 23:07:30.960: INFO/DEBUG(510): #05 pc 002a4db4 /
system/lib/libwebcore.so
01-31 23:07:30.970: INFO/DEBUG(510): #06 pc 001a6146 /
system/lib/libwebcore.so
01-31 23:07:30.970: INFO/DEBUG(510): #07 pc 002a5880 /
system/lib/libwebcore.so
01-31 23:07:30.980: INFO/DEBUG(510): #08 pc 00359e5e /
system/lib/libwebcore.so
01-31 23:07:30.990: INFO/DEBUG(510): #09 pc 0035d336 /
system/lib/libwebcore.so
01-31 23:07:31.001: INFO/DEBUG(510): #10 pc 003638ea /
system/lib/libwebcore.so
01-31 23:07:31.001: INFO/DEBUG(510): #11 pc 0019f70a /
system/lib/libwebcore.so
01-31 23:07:31.011: INFO/DEBUG(510): #12 pc 0019f790 /
system/lib/libwebcore.so
01-31 23:07:31.020: INFO/DEBUG(510): #13 pc 001a3d9a /
system/lib/libwebcore.so
01-31 23:07:31.020: INFO/DEBUG(510): #14 pc 001a3efa /
system/lib/libwebcore.so
01-31 23:07:31.040: INFO/DEBUG(510): #15 pc 001af386 /
system/lib/libwebcore.so
01-31 23:07:31.040: INFO/DEBUG(510): #16 pc 00017d34 /
system/lib/libdvm.so
01-31 23:07:31.040: INFO/DEBUG(510): #17 pc 00048f0c /
system/lib/libdvm.so
01-31 23:07:31.050: INFO/DEBUG(510): #18 pc 00041aca /
system/lib/libdvm.so
01-31 23:07:31.050: INFO/DEBUG(510): #19 pc 0002972c /
system/lib/libdvm.so
01-31 23:07:31.060: INFO/DEBUG(510): #20 pc 00020fe0 /
system/lib/libdvm.so
01-31 23:07:31.060: INFO/DEBUG(510): #21 pc 0005f360 /
system/lib/libdvm.so
01-31 23:07:31.070: INFO/DEBUG(510): #22 pc 0005f586 /
system/lib/libdvm.so
01-31 23:07:31.070: INFO/DEBUG(510): #23 pc 00053b06 /
system/lib/libdvm.so
01-31 23:07:31.080: INFO/DEBUG(510): #24 pc 00011a7c /
system/lib/libc.so
01-31 23:07:31.090: INFO/DEBUG(510): #25 pc 00011640 /
system/lib/libc.so
01-31 23:07:31.090: INFO/DEBUG(510): code around pc:
01-31 23:07:31.090: INFO/DEBUG(510): 81d459e0 447a4479 ed0cf7d1
20004c09 ee34f7d1
01-31 23:07:31.090: INFO/DEBUG(510): 81d459f0 447c4808 6bdb5823
d0002b00 49064798
01-31 23:07:31.090: INFO/DEBUG(510): 81d45a00 700a2226 eea0f7d1
0004361f 000451dd
01-31 23:07:31.090: INFO/DEBUG(510): 81d45a10 0005ebd2 fffffebc
deadd00d b510b40e
01-31 23:07:31.100: INFO/DEBUG(510): 81d45a20 4c0a4b09 447bb083
aa05591b 6b5bca02
01-31 23:07:31.100: INFO/DEBUG(510): code around lr:
01-31 23:07:31.100: INFO/DEBUG(510): afd19354 b0834a0d 589c447b
26009001 686768a5
01-31 23:07:31.100: INFO/DEBUG(510): afd19364 220ce008 2b005eab
1c28d003 47889901
01-31 23:07:31.100: INFO/DEBUG(510): afd19374 35544306 d5f43f01
2c006824 b003d1ee
01-31 23:07:31.110: INFO/DEBUG(510): afd19384 bdf01c30 000281a8
ffffff88 1c0fb5f0
01-31 23:07:31.110: INFO/DEBUG(510): afd19394 43551c3d a904b087
1c16ac01 604d9004
01-31 23:07:31.110: INFO/DEBUG(510): stack:
01-31 23:07:31.120: INFO/DEBUG(510): 43f3f5e0 00000015
01-31 23:07:31.120: INFO/DEBUG(510): 43f3f5e4 afd18407 /system/
lib/libc.so
01-31 23:07:31.120: INFO/DEBUG(510): 43f3f5e8 afd4270c /system/
lib/libc.so
01-31 23:07:31.120: INFO/DEBUG(510): 43f3f5ec afd426b8 /system/
lib/libc.so
01-31 23:07:31.130: INFO/DEBUG(510): 43f3f5f0 00000000
01-31 23:07:31.130: INFO/DEBUG(510): 43f3f5f4 afd19375 /system/
lib/libc.so
01-31 23:07:31.130: INFO/DEBUG(510): 43f3f5f8 002a1af8 [heap]
01-31 23:07:31.130: INFO/DEBUG(510): 43f3f5fc afd183d9 /system/
lib/libc.so
01-31 23:07:31.140: INFO/DEBUG(510): 43f3f600 002a2dc0 [heap]
01-31 23:07:31.140: INFO/DEBUG(510): 43f3f604 0005ebd2 [heap]
01-31 23:07:31.140: INFO/DEBUG(510): 43f3f608 405e7900 /dev/
ashmem/dalvik-heap (deleted)
01-31 23:07:31.140: INFO/DEBUG(510): 43f3f60c 81d859ec /system/
lib/libdvm.so
01-31 23:07:31.140: INFO/DEBUG(510): 43f3f610 002a2dc0 [heap]
01-31 23:07:31.140: INFO/DEBUG(510): 43f3f614 afd18437 /system/
lib/libc.so
01-31 23:07:31.140: INFO/DEBUG(510): 43f3f618 df002777
01-31 23:07:31.150: INFO/DEBUG(510): 43f3f61c e3a070ad
01-31 23:07:31.150: INFO/DEBUG(510): #00 43f3f620 00000001
01-31 23:07:31.160: INFO/DEBUG(510): 43f3f624 81d37701 /system/
lib/libdvm.so
01-31 23:07:31.160: INFO/DEBUG(510): #01 43f3f628 00000001
01-31 23:07:31.160: INFO/DEBUG(510): 43f3f62c 81d399c9 /system/
lib/libdvm.so
01-31 23:07:34.681: INFO/DEBUG(510): debuggerd committing suicide to
free the zombie!
01-31 23:07:34.741: INFO/DEBUG(618): debuggerd: Jan 19 2011 16:46:23
01-31 23:07:34.881: DEBUG/Zygote(33): Process 603 terminated by signal
(11)
01-31 23:07:34.901: INFO/ActivityManager(76): Process
com.drrosey.games.dr_rosey_math_mole_ultimate (pid 603) has died.
01-31 23:07:34.911: INFO/WindowManager(76): WIN DEATH: Window{405a5d98
com.drrosey.games.dr_rosey_math_mole_ultimate/
com.drrosey.games.dr_rosey_math_mole_ultimate.DrRoseyMathMoleUltimate
paused=false}
01-31 23:07:35.140: INFO/ActivityManager(76): Low Memory: No more
background processes.
01-31 23:07:35.320: WARN/InputManagerService(76): Got RemoteException
sending setActive(false) notification to pid 603 uid 10030
01-31 23:07:40.951: DEBUG/skia(168): purging 7K from font cache [1
entries]
01-31 23:07:41.020: DEBUG/dalvikvm(168): GC_EXPLICIT freed 6K, 52%
free 2725K/5639K, external 2108K/2632K, paused 66ms
01-31 23:07:46.041: DEBUG/dalvikvm(165): GC_EXPLICIT freed 5K, 53%
free 2929K/6151K, external 1625K/2137K, paused 84ms
01-31 23:07:50.971: DEBUG/skia(237): purging 12K from font cache [1
entries]
01-31 23:07:51.071: DEBUG/dalvikvm(237): GC_EXPLICIT freed 2K, 49%
free 2951K/5767K, external 7693K/9607K, paused 97ms
01-31 23:07:55.981: DEBUG/skia(76): purging 74K from font cache [8
entries]
01-31 23:07:56.141: DEBUG/dalvikvm(76): GC_EXPLICIT freed 740K, 61%
free 4062K/10247K, external 3522K/3903K, paused 159ms
01-31 23:08:05.101: DEBUG/dalvikvm(161): GC_EXPLICIT freed 1K, 54%
free 2590K/5575K, external 1625K/2137K, paused 59ms

Math-on-Phone

unread,
Feb 1, 2011, 12:37:31 AM2/1/11
to phonegap
To add to this it appears that 2.2.1 and 2.3 have this problem with
the javascript bridge. Here's some banter at appcelerator's forum:

http://developer.appcelerator.com/question/88861/applications-will-crash-when-using-webviews-on-android-221-and-23

-- Aaron

On Jan 31, 11:41 pm, Math-on-Phone <mathonph...@gmail.com> wrote:
> Hi Everyone,
>
> My relatively simple "Math-a-Mole" app has been rejected from Amazon
> Marketplace. I believe it is related to the "javascript bridge" issue
> also known as the "Gingerbread 2.3 emulator" issue. I have reason to
> believe the problem is more widespread and affects real hardware too.
>
> Here are the exact words from the Amazon testing team:
>
> "- App fails to launch successfully on Droid Incredible 2.2. When
> launched, a message appears (to quick to read) and then phone's screen
> goes black. No other message or image appears."
>
> Interesting eh? They say 2.2 there but the "popular" consensus is that
> this only happens in 2.3 emulator and not even on a 2.3 phone.
>
> Here in the phonegap lighthouse app we say this issue is "invalid"
> since it is a breakage on Google's side:
>
> http://phonegap.lighthouseapp.com/projects/20118/tickets/61-sample-ap...

Jaco Smit

unread,
Feb 1, 2011, 3:33:18 AM2/1/11
to phon...@googlegroups.com
what is the sollution? any sollutions?

--
You received this message because you are subscribed to the Google
Groups "phonegap" group.
To post to this group, send email to phon...@googlegroups.com
To unsubscribe from this group, send email to
phonegap+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/phonegap?hl=en?hl=en

For more info on PhoneGap or to download the code go to www.phonegap.com

Math-on-Phone

unread,
Feb 1, 2011, 8:36:59 AM2/1/11
to phonegap
Hi Jaco,

As far as I know, there are no solutions. I'm hoping to illicit
feedback from someone who at least has shaken hands with the
developers at Google in the past. It appears that the Google team does
not take this seriously. They consider this a "medium" priority update
but of course for us it is a show stopper. The recent release of the
2.3.1 emulator has not rectified this problem! It is also not limited
to the emulator, some real phones running variants of the 2.2 Android
OS exhibit the same behavior (Droid Incredible 2.2, ZTE Blade).

This issue has had a reduction since at least Dec. 06, 2010. Google
needs to take action. However "only" 236 people have "starred" the
issue indicating it is serious for them. While the problem stops us
cold we are still the pioneers in this brave new frontier of the
javascript - java bridge. Many other apps run fine on these newer
phones.

-- Aaron

Yoel Gluschnaider

unread,
Mar 20, 2011, 4:39:12 AM3/20/11
to phonegap
Found this workaround, didn't try it yet but it might solve the issue:

http://quitenoteworthy.blogspot.com/2010/12/handling-android-23-webviews-broken.html

Also, look at remark 14 here: http://code.google.com/p/android/issues/detail?id=12987

It points out problems in this solution...

On Feb 1, 10:33 am, Jaco Smit <icephixia2...@gmail.com> wrote:
> what is the sollution? any sollutions?
>
>
>
>
>
>
>
> On Tue, Feb 1, 2011 at 7:37 AM, Math-on-Phone <mathonph...@gmail.com> wrote:
> > To add to this it appears that 2.2.1 and 2.3 have this problem with
> > the javascript bridge. Here's some banter at appcelerator's forum:
>
> >http://developer.appcelerator.com/question/88861/applications-will-cr...
> > phonegap+u...@googlegroups.com<phonegap%2Bunsubscribe@googlegroups.c om>

Bryce Curtis

unread,
Mar 21, 2011, 2:20:21 PM3/21/11
to phonegap
A workaround for the 2.3 JavaScript bridge issue has been implemented
in the latest github code. The fix will be in v0.9.5 when released.
If you want to use it now, you can download the source from github and
rebuild jar and js files.

Regards,
Bryce

On Mar 20, 3:39 am, Yoel Gluschnaider <yoelg...@gmail.com> wrote:
> Found this workaround, didn't try it yet but it might solve the issue:
>
> http://quitenoteworthy.blogspot.com/2010/12/handling-android-23-webvi...
> > > phonegap+u...@googlegroups.com<phonegap%2Bunsubscr...@googlegroups.c om>

Jehandad Kamal

unread,
Apr 18, 2011, 10:30:46 AM4/18/11
to phon...@googlegroups.com
I am beginner android developer. I have seen your code on github but It not understandable for me. Can you guide me a little. Adding JavaScript files is understandable. But I am trying to use your solution in a simple activity. 

Appreciate your time. Thanks.
Reply all
Reply to author
Forward
0 new messages