Note that I have merged the sub-develop branches (timelines and markov) back up into develop, and will shortly be deleting those branches.

So anyone pointing their Podfile at timelines should update their Podfile to point to develop again.

I will be looking to merge back to master soon too, but that will require a bit more spare time than I have right now, due to needing to docu

The following things should be fixed:

• Inserts that trigger an upsert should be logged as an update
• An update should log the identifier/value the old value (or none) and the new value, eg: column: old => new
• Avoid duplicate code for scoped/unscoped that only differ in color codes

Also, consider:

• Reuse the one-line representation in select as a base for detailed

🏗 Enhancement Proposal

Currently on iOS background location updates are enabled by default and cannot be turned off. This might result into Apple rejecting a submitted app because it the developer doesn't need support for background location updates and thus didn't specify any justification for this.

Pitch

The pitch is basically to apply the following two changes:

1. Make sure t

The ActivityRecognitionApi interface is now deprecated.

The recommended implementation is to "Use the connectionless API ActivityRecognitionClient instead."

I have notice

on zoom your script trows a TypeError: this._marker is undefined if drawMarker: false. not sure about the rest of the code

https://github.com/domoritz/leaflet-locatecontrol/blob/9bffaa4c171484df148ab301fa8e480e6e481774/src/L.Control.Locate.js#L777

Environment

System:
OS: Linux 4.15 Ubuntu 18.04.3 LTS (Bionic Beaver)
CPU: (8) x64 Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
Memory: 597.36 MB / 7.70 GB
Shell: 4.4.20 - /bin/bash
Binaries:
Node: 10.18.1 - /usr/bin/node
Yarn: 1.21.1 - /usr/bin/yarn
npm: 6.13.6 - /usr/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
AP

The documentation fails to mention that when using storyboards, the LocationPicker controller should be embedded in its own navigation controller as well if 'Done' and 'Cancel' buttons are used. Otherwise, the 'parent' navigation controller is dismissed due to the call to dismissViewControllerAnimated.

Alternatively, the code could check whether LocationPicker is the root view controller and i

From the docs:
"Declared elements are informational only, meaning that the Android system itself does not check for matching feature support on the device before installing an application"

We should consider making our hardware requirements optional and have application developers declare these valu

安卓7.1.1
小米6
复现步骤: 先打开example.apk, 然后打开摩拜单车APP
java.lang.RuntimeException: Error receiving broadcast Intent { act=permission check ok flg=0x10 } in cn.qiuxiang.react.baidumap.modules.BaiduMapInitializerModule$SDKReceiver@dffceae
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1138)
at android.os.Handler.handleCallback(Handler.java:754)
at android.os.Handler.dispatchM

Please indicate which of these features will be allowed by Apple/Google for apps to be provided via the app store / play store?
Is it possible to include feature to turn on/off Airplane mode, or DND, from within an app (assuming correct permission) and have Apple/Google not reject the app?
Also, can this library used with an Expo managed app, or does it require 'eject'?

Thanks