MobileFirst Geo-trigger "dwellInside" callback not invoked - ibm-mobilefirst

I am working with the Mobile First Platform studio 7.1 and following the documentation on location services here Documentation. I am doing all my testing with the Mobile Browser Simulator.
I have noticed that while testing with the MBS the callback functions for the sample (DwellInside) are not getting invoked. For example, the app says that an alert will displayed if the location has changed in the last 3 seconds.
I have created a sample application similar)to the one that can be downloaded from the "Documentation" link here:MyCode
My version(which is just gets the locations and does a DwellInside) also cannot get the call back to be invoked.
Is there something that I am missing? Please advise.

To not leave a question unanswered, as mentioned by #user2674117 in the comments:
you will need to pass it new coordinates after startAcquisition. New triggers are evaluated the first time a new coordinate is supplied; it doesn't assume the last given position is necessarily current.

Related

The number of times a custom event happened is not being updated on my dashboard

I've been able to distinguish between the live build and the test build on my Android app. Everything works perfectly on the test version. I can see the live events and when I go and see the number of clicks for an event, that gets updated too. However, on the live build of my app, I can see the live events but the number of clicks is not being updated. All the events still show empty analytics. What could be wrong?
Amruta from Branch.io here:
Based on your description it looks like your App is still using the test key. If your App has both the Live and Test key added to the Manifest, and you have the debug mode enabled, your App will continue using the Test key. You should make sure that your App is using the Live key.
You can ensure that your app is using the Live key by using a Branch link from the Live version of your App. On clicking on the link, the link parameters received in the callback should have the parameter '+clicked_branch_link: true'.
If the parameter 'clicked_branch_link' is set to false it means that your App is still using the test key.
If you still continue to face issues, I would suggest writing to integrations#branch.io and they can help you resolve any issues you are facing.

Durandal Get Started Sample

I've tried following the Get Started example from the Durandal homepage, and just get..
I've refreshed the files from the Starter app / example, and followed the Get Started tutorial once a few weeks ago, and twice again today, and just get the numbers as above, not the expected form to type a name into.
Where do I even go to start debugging this issue?
I would start by pressing "F12" and opening the browser debugging console, to see if all the files have come down. There may even be some syntax errors as well.
The HotTowel template by John Papa is also worth a look.
If you are just starting out with Durandal, also have a look at Aurelia, which is effectively the next version of Durandal.

MarkerWithLabel stopped working correctly

All of a sudden yesterday 3/4/2014 my MarkerWithLabel (Google map API application) is only showing the last marker but the labels all show up. It had been working just fine. The Google Example at: https://google-maps-utility-library-v3.googlecode.com/svn/tags/markerwithlabel/1.0.1/examples/basic.html is not working at all and I based my code on this example that used to work just fine.
In link below I placed 2 markers with labels on a map. Only marker 2 displays while both labels display. Reversing the markers causes marker 2 to display but not marker 1. Both labels display.
What changed or what am I doing wrong?
You can see my problem first hand at http://qsomap.org/QSOmapProduction/labeltest.htm . This was working correctly 2 days ago.
It appears as if the latest google maps update broke something that markerwithlabel code relies on. The same thing happend to some of my maps. We'll have to wait until a fix is available.
The current solution is to set the google maps API version to 3.15 or lower:
https://code.google.com/p/google-maps-utility-library-v3/issues/detail?id=296&sort=-id&colspec=ID%20Type%20Status%20Priority%20Fixed%20Owner%20Summary%20Stars
Using ...maps.google.com/maps/api/js?sensor=false&v=3.15 works
Using ...maps.google.com/maps/api/js?sensor=false&v=3.16 goes wrong
Using ...maps.google.com/maps/api/js?sensor=false goes wrong as well
The most recent Google API update (4th APR 2018) has broken my version of MarkerWithLabel. I have not yet tested MarkerWithLabel 1.9.1, but it is still the current and most recent update (I was on an older build). Here is a link to the latest version:
https://github.com/googlemaps/v3-utility-library/tree/master/markerwithlabel
I have reverted to an older version by including &v=3.31 in the URL and this has restored functionality, many thanks to #Mikrohard for the tip.
I'm not moving until I've investigated if the update has broken other libraries such as map clusters.

How to re-allow my app to use the current location

I am using CLLocationManager to find the location.The first time that I run the app for mistake I didn't allow the app to use the current location.
So every time the delegate gets notified through the locationManager:didFailWithError selector.
I tried to make a clean build and to delete the project folder in derived data, but it still doesn't ask me to use the current location.
I would make possibile to re-select through that panel if I would use the location, how is that possibile?
You have to delete the application from the simulator or phone and then run another build onto the device.
I hope I understood you correctly, if I think that this is not a coding issue:
If you are on iOS6, you'll have to allow location services for the app at
Settings > Privacy > Location Services.
For more info, see Apple's documentation here: http://support.apple.com/kb/HT5467?viewlocale=en_US&locale=en_US

Safari 6's New Developer Toolbar doesn't show Form Data in XHR/AJAX Requests

Safari recently went to version 6 (Lion/Mtn Lion) and they've changed over from the standard webkit dev tools to one that's much more XCode looking, my problem other than the OCD of not liking things change is that in the resource tab (or anywhere you can track down the DataService.aspx/AJAX calls) I can no longer see the form data that I am passing.
Can anyone point me to where I can find that data so I don't have to console out my params when I'm testing new data service/backend calls?
I've logged a bug with Apple, they've marked it as a duplicate so hopefully they've received enough requests to fix this, until then I'm continuing to use chrome as the webkit developer is the same as safari's old version.
You can find this info in Instrument tab (stop-watch icon). In the left sidebar thers Timelines row, click the grey circle (record button) on the right. Then click to Network Requests where you see all reqs, and you have to click small icon on the right oc request to display response headers and all form data are available in right panel. Panel can be hidden same as left one (in case you dnt see it).
Unfortunately there are no query pamaters listed, according to this disscussion. I belive its a bug in safari
Edit 15.May 2013: This bug was fixed in Safari 6.0.3.
As far as I can tell, there's no way to show the request parameters.
This goes even further. I can't see the JSON response data either (no clickable arrows to show the containing Javascript objects within the JSON, just pure text)
I think we have to switch to Firefox /w Firebug or regular Webkit in order to get XHR monitoring...
Guys if you want to see post data in safari 6 which is not possible right now, install the firebug lite extension and there you go you have the post data.
I used it and it works great with safari 6
Actually the request headers, response headers and query parameters are in the details sidebar on the right when using the resources view or if you click to see the content of a request in the Timelines/Network Requests view. Took me a few minutes to find that too.
If you need to see what the device is actually sending and your server is on a Windows Machine I use http://www.Wireshark.org and check on the server side of things. No interpretation by any WebKit stuff and very valuable (such as issue with iOS and the 'Blob' data). Similar network snooping should exist on Mac as well.