kailIII / android-notifier

Automatically exported from code.google.com/p/android-notifier
0 stars 0 forks source link

force close remote-notifier 0.2.6 #157

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
IMPORTANT: PLEASE search the existing issues (including closed ones) for
something similar before filing a new one.

What steps will reproduce the problem?
1. pair phone and computer - authorize phone to access any bluetooth services 
on computer
2. open android-desktop-notifier 
3. send test notification in remote-notifier on phone
4. force close occurs

What is the expected output? What do you see instead?
expected to see test notification sent
remote-notifier force closes

What version of the product are you using? On what operating system?
Samsung Galaxy S with Froyo I9000XXJPC rom
Windows XP SP3 32-bit & android-notifier-desktop 0.4.0
Growl for Windows v2.0.4

attached are logcat from Android phone

Please provide any additional information below.

Original issue reported on code.google.com by luke.a.i...@gmail.com on 20 Sep 2010 at 12:43

Attachments:

GoogleCodeExporter commented 9 years ago
It's not clear - is the force close on the android app or on the desktop app?

Original comment by rdamazio@gmail.com on 20 Sep 2010 at 7:38

GoogleCodeExporter commented 9 years ago
Ok, from the logs it looks like it's the Android app, sorry about that.
Indeed I see other reports on the android market:
java.lang.NullPointerException
at 
org.damazio.notifier.notification.BluetoothNotificationMethod.doSendNotification
(BluetoothNotificationMethod.java:154)
at 
org.damazio.notifier.notification.BluetoothNotificationMethod.sendNotification(B
luetoothNotificationMethod.java:95)
at 
org.damazio.notifier.notification.Notifier.runNotificationThread(Notifier.java:6
9)
at org.damazio.notifier.notification.Notifier.access$0(Notifier.java:65)
at org.damazio.notifier.notification.Notifier$1.run(Notifier.java:54)

Original comment by rdamazio@gmail.com on 20 Sep 2010 at 7:41

GoogleCodeExporter commented 9 years ago
Found it :)

Original comment by rdamazio@gmail.com on 20 Sep 2010 at 7:44

GoogleCodeExporter commented 9 years ago
Fixed in r268. Thanks for reporting.

Original comment by rdamazio@gmail.com on 20 Sep 2010 at 7:47

GoogleCodeExporter commented 9 years ago
yep - i fixed the issue by uninstalling 0.2.5 and then installing 0.2.6

must be something up with the upgrade

is r268 available in the market?

Original comment by luke.a.i...@gmail.com on 20 Sep 2010 at 9:16

GoogleCodeExporter commented 9 years ago
Not yet - it will be in the next version.

Original comment by rdamazio@gmail.com on 20 Sep 2010 at 2:08