v2.2.1

Second alpha release for the Microsoft Embedded Social integration. Based on WIP pull request #744.

UPDATE - Rejected by Google Play due to security vulnerability detected by Google Play in Embedded Social library:

onReceivedSslError
 
Detected in APK 82
Your app is using an unsafe implementation of WebViewClient.onReceivedSslError handler. Please see this Google Help Center article for details, including the deadline for fixing the vulnerability.
Vulnerable classes:
•	com.microsoft.a.d$a$a

versionCode 82

v2.1.9

Released to staged rollout first and full release as new production version May 8, 2017.

Enhancements:

• #697 - Allow users to opt out of "Location not enabled" dialog
• Trip Planning (Puget Sound) - no code change for this - it's been configured in the Regions API as a gradual rollout, but this update will force all users to refresh Regions API and they will see the feature

Bug fixes:

• #600 - Remove Google Play Services license info from About
• #770 - Get release password via dialog when Gradle runs as daemon

versionCode 76

v2.2.0

First alpha release for the Microsoft Embedded Social integration. Based on WIP pull request #744.

Improvements:

• Social discussions - Chat with other OneBusAway users about stops and routes!

versionCode 81

v2.1.8

Released to Google Play

Improvements:

• #763 - Add block_id to Open311 issue report metadata
• Update FAQ documentation

versionCode 75

v2.1.7

Initially released to production at 5% to replace 2.1.6 due to #749, and then pushed to all users.

Improvements:

• Improve trip plan notification text
• #671 - Add trip plan start/end markers
• #756 - Improve trip start/end marker implementation
• #746 - Tell user to check Internet connection for OBA 500 errors
• #747 - Only show trip plan report button if we get a server response

Bug fixes:

• Fix #752 - Ensure correct itinerary is selected when app is backgrounded and resumed
• Fix #749 - Use primitives instead of Serializables in Bundles for AlarmManager (Fix crash when checking in background for improved trip plan)

versionCode 74

v2.1.6

Enhancements:

• #738 - Add left handed mode

Bug fixes:

• Fix #655 - Change RealtimeService to use WakefulBroadcastReceiver and Intent Services. Enables trip plan reminders to occur even after one has left the trip planning screen.
• Fix #742 - Normalize formatting for stop, route, and headsign text
• Fix #496 - Correctly reflect arrival/departure information in reminder text
• Fix #737 - Bump fresh location threshold so test passes
• Fix #731 - Make arrival time issue report headsign Title Case
• Fix #730 - Properly scale image for issue reports

Performance improvements:

• #687 - Load uncolored vehicle markers on demand

Halted production rollout at 5% due to #749.

v2.1.5

Released as beta and to production on Google Play.

Enhancements:

• #713 - Allow user to hide alerts
• #717 - Support transit-only Open311 deployments
• #578 - Show progress bar on map when loading stops/routes
• #710 - Support service alert URLs
• Code cleanup

Bug fixes:

• Fix #706 - Properly manage visibility of customer service buttons
• Fix #722 - Apply title case to stop name in trip status view
• Fix report stop header string name
• Increase padding between alert (situation) icon and title

v2.1.4

Release as a beta and then staged release on Google Play. If no issues are found will be released to production and Amazon Fire Phone.

Enhancements:

• #411 - Add vehicle markers for boat, train, subway, and tram

Bug fixes:

• Fix #700 - Show route-specific service alerts
• Fix #683 - Ensure StopOverlay/Map has been initialized prior to setting focused stop
• Fix #662 - Workaround - don't use leg.tripShortName in directions
• Fix #677 - Implement proper Up navigation for TripPlanActivity
• Fix #688 - Imitate back behavior for UP navigation from ServiceAlertActivity
• Fix #691 - Check for null headsign for formatting it
• Fix #690 - Check if headsign is null before querying route favorite
• Fix #673 - Use Application context when checking if route headsign is a favorite
• Fix #669 - Use Application context to add/update stop table in database
• Fix #674 - Add null check for header before updating with trip info

v2.1.3

Released on Google Play

Enhancements, including:

• #668 - Make "What's New" URLs clickable
• #627 - Add stop direction with stop name
• #622 - Add a custom trip planning API URL setting
• #656 - Add GA event for trip plan requests sent to a server
• #634 - Add stop name to metadata posted to Open311 server
• #618 - Add trip plan problem reporting

Bug fixes, including:

• Fix #579 again - Auto-center on location using default zoom
• Fix #428 - Set the map vehicle marker zIndex to be on top of stop markers
• Fix #640 - Add null checks before redrawing navigation drawer
• Fix #664 - Check if region is null before biasing geocoding results
• Fix #635 - Add null check before accessing otpBaseUrl
• Fix #632 - Add null check when removing trip planning notification preference
• Fix #561 - Correctly format headsign in vehicle marker balloon
• Fix #653 - Pass in Class instead of Activity reference for trip plan notification target
• Fix #652 - Refactor constructor variables to the correct names
• Fix #611 - Trip planning - format "Leaving" text

v2.1.2

Hotfix published straight to staged rollout on Google Play. Will publish to Amazon if no issues.

Bug fixes:

• Crash on zoom to region (Fix #581)
• Custom API Settings crash (Fix #635 - Add null check before accessing otpBaseUrl)
• Home screen shortcuts not going directly to arrivals screen (Fix #626 - Make home screen shortcuts always launch Activities on top). Shortcuts must be recreated for this to take effect.