Forum | Appery.io

Created a brand new project.

Added a button.

Added Click event to button.

When clicked, runs custom JS:
navigator.notification.beep(2);

Nothing happens.

Also tried:
navigator.notification.vibrate(1000);

I'm using the Mobile Tester for iOS on an iPhone 4s. iOS 5.1

I don't really need beeps and vibrates, but I'm trying to assess whether or not something is broken, or if I'm just doing it wrong before diving into what I actually need to do.

Thanks Max!

When did you get the sources for iOS tester..? We had such bug but it's now fixed. Get new iOS tester sources, build it and try again.

Just grabbed the most recent copy off the site. 1.1.
Still doesn't seem to want to cooperate.

I completely deleted everything from the sample project and added it back exactly the way it was.

Seems to work now. Odd, but at least I've got beeps.

Guess I spoke too soon, not working again.
I tried removing everything from the project and adding back the single button with a click event, but it's no go.

Is it possible that something is getting cached somewhere?

When I did add a button and make it beep, I tried adding a second button for vibrate and the vibrate wouldn't work while the beep did.

Same for alert & confirm notifications. Neither of those worked, while beep did.

Too weird.

Aha! Ok, I think I've narrowed this down. It's not the web UI at all, it's an issue with the tester (I think).

Steps to reproduce for me:

1. Create a new project

2. Add a button with a click event to beep via navigator.notification.beep(2);

3. Save & Test Project. Button works on tester.

4. Add a button with a click event to vibrate via navigator.notification.vibrate(1000);

5. Save & Test Project. Beep button works, vibrate button does not work. (Nor any additional buttons added after).

6. Force close the tester app. (Hold power button until power off screen comes up, then hold home button until app closes).

7. Re-Open Tiggzi Tester and launch app. Both buttons work.

   So, I'm not sure if something just isn't getting updated when the app is relaunched or what, but a force close seems to fix it. Just exiting normally via the home button does not. At least not when I tried it. Unfortunately this makes testing a little more tedious, but still way better than having to do it manually.

   Sorry for so many responses, to my own question but I don't want anyone chasing their tail so to speak if I've got more info to share.

   Thanks again!

Hello Ryan,

This is a bug of iOS Tiggzi Tester, we are working on fixing it.

Awesome, thank you very much. Good to know it's not user error and that I'm really NOT just going nuts.

It's now fixed. You can get the updates source from: http://subversion.exadel.org/repos/ti...

Thanks!