The devDependency @commitlint/cli was updated from 7.5.0 to 7.5.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@commitlint/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency rollup was updated from 1.6.0 to 1.6.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency eslint-config-axway was updated from 4.1.1 to 4.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-axway is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency webpack was updated from 4.21.0 to 4.22.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Describe the bug
After upgrading to Titanium SDK 8.0.0.GA from 7.5.0.1GA the app icon on android went back to titaniums default icon when running on Android.

Expected behavior
The app should use the icon provided.

Environment
Titanium CLI
CLI Version = 5.1.1
Titanium SDK
SDK Version = 8.0.0.GA

The devDependency rollup-plugin-commonjs was updated from 9.2.3 to 9.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup-plugin-commonjs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency node-titanium-sdk was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-titanium-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency danger was updated from 6.1.10 to 6.1.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

danger is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency node-titanium-sdk was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-titanium-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency node-appc was updated from 0.3.1 to 0.3.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-appc is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency rollup-plugin-commonjs was updated from 9.3.0 to 9.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup-plugin-commonjs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

In a nutshell, I'm looking to explicitly bind a socket to a particular network interface (e.g.: force TCP traffic over WiFi connection even when internet is not available so as to avoid defaulting to over cellular connection). The following missing feature should make that possible.

Android's ConnectivityManager has a method bindProcessToNetwork():

Binds the current process to network. All Sockets created in the future (and not explicitly bound via a bound SocketFactory from Network.getSocketFactory()) will be bound to network. All host name resolutions will be limited to network as well. Note that if network ever disconnects, all Sockets created in this way will cease to work and all host name resolutions will fail. This is by design so an application doesn't accidentally use Sockets it thinks are still bound to a particular Network. To clear binding pass null for network. Using individually bound Sockets created by Network.getSocketFactory().createSocket() and performing network-specific host name resolutions via Network.getAllByName is preferred to calling bindProcessToNetwork.

See: https://developer.android.com/reference/android/net/ConnectivityManager#bindProcessToNetwork(android.net.Network)

As the reference describes, it would be better to do the binding at the socket level. In order to do that, however, the network-specific host name resolutions need to be made available via Network.getAllByName() and then passed to createSocket(host, port, localHost, localPort). These features are not exposed by Ti.Network module.

It does appear that https://github.com/appcelerator/titanium_mobile/blob/master/android/modules/network/src/java/ti/modules/titanium/network/TiSocketFactory.java#L101 has support for the extra parameters though the are not documented. I'm assuming the dict for Ti.Network.Socket.createTCP() could be expanded to include the localHost and localPort params. Ti.Network.getAddressForType('wifi')could be added to facilitate getting the needed localHost address for that network interface. Then it would all come together as Ti.Network.Socket.createTCP({ ..., localHost: Ti.Network.getAddressForType('wifi')}).

If this isn't a good way of dealign with this need, then how would I go about binding a network interface to a TCP socket so that traffic is forced to use the WiFi connection instead of the concurrently enabled Cellular connection which won't reach the WiFi AP.

The devDependency rollup was updated from 1.8.0 to 1.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency rollup was updated from 1.9.2 to 1.9.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency husky was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

husky is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @commitlint/cli was updated from 7.2.1 to 7.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@commitlint/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency grunt was updated from 1.0.3 to 1.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency commitizen was updated from 3.0.7 to 3.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

commitizen is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency fs-extra was updated from 7.0.0 to 7.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

fs-extra is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency eslint-plugin-mocha was updated from 5.2.0 to 5.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency js-yaml was updated from 3.12.0 to 3.12.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

js-yaml is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency colors was updated from 1.3.2 to 1.3.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

colors is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency grunt-cli was updated from 1.3.1 to 1.3.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency copy-webpack-plugin was updated from 4.5.3 to 4.5.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

copy-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency node-titanium-sdk was updated from 3.0.0 to 3.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-titanium-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Problem:

If you try to compile for iOS with the latest SDK 8 release, you will get a BUILD FAILED error during xcodebuild if your filesystem is case sensitive, because Xcode can't build the TitaniumKit module.

This happens because of wrong or not uniform naming of the 'Webcolor' file(s) / references. Sometimes it's called 'Webcolor', sometimes it's called 'WebColor'.

Expected result:

All occurrences should be renamed to 'WebColor' on all places to make it similar to all other files and to get a uniform file naming convention - and to prevent possible issues with case sensitive file systems in the future.

System used:

macOS Mojave 10.14.3
Titanium SDK 8.0.0.GA
Xcode 10.2

The devDependency danger was updated from 7.0.14 to 7.0.15.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

danger is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency node-titanium-sdk was updated from 3.0.1 to 3.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-titanium-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @commitlint/config-conventional was updated from 7.5.0 to 7.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@commitlint/config-conventional is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency danger was updated from 7.0.19 to 7.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

danger is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency pngjs was updated from 3.3.3 to 3.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

pngjs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency lint-staged was updated from 8.1.5 to 8.1.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency js-yaml was updated from 3.13.0 to 3.13.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

js-yaml is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency rollup-plugin-node-resolve was updated from 4.0.1 to 4.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup-plugin-node-resolve is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency commander was updated from 2.19.0 to 2.20.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

commander is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Describe the bug

Hi! I'm writing from the Android team.
Appcelerator Ti does not safely deal with the addition of the mapping from file extension "json" to MIME type "application/json" in Android Q, leading to Android Q-specific problems at runtime observed in at least four different apps. In one app, it looks like there may be an issue in JavaScript code trying to JSON.parse() an already-parsed JSON object (ie. which has already gone through JSON.parse()). The JavaScript source code isn't clear - it might be bundled with Appcelerator Ti, or it might be app code (perhaps going through TiVerify).

To Reproduce
Unfortunately you'll have to find an affected app yourself (not sure if I should disclose particular apps here), but it shouldn't be too difficult because most of the ones I checked are affected.

1. Use Android Q Beta from https://developer.android.com/preview
2. Start an app built on top of Appcelerator Ti.
3. Unfortunately the behavior differs from app to app. Some show error dialogs, some show stacktraces such as the below examples.

Expected behavior
Apps work normally and do not show any error dialogs / log any errors.

Environment
Observed on various versions of Appcelerator Ti, eg. 7.0.2 and 7.5.0

Logs:
One app:

TiExceptionHandler: (main) [22,246] [object TiBlob]
TiExceptionHandler: ^
TiExceptionHandler: SyntaxError: Unexpected token o in JSON at position 1
TiExceptionHandler: at JSON.parse ()
TiExceptionHandler: at Object.exports.loadTiLangFile (/lib/shared/lang.js:94:13)
TiExceptionHandler: at Object.exports.loadLangFile (/lib/shared/lang.js:80:19)
TiExceptionHandler: at Object.exports.getString (/lib/shared/lang.js:131:41)
TiExceptionHandler: at Object.exports._ (/lib/shared/lang.js:172:13)
TiExceptionHandler: at ConnectionEvents (/events/connection.js:9:19)
TiExceptionHandler: at /app.js:45:29
TiExceptionHandler: at Module._runScript (ti:/module.js:613:9)
TiExceptionHandler: at Module.load (ti:/module.js:105:7)
TiExceptionHandler: at Module.loadJavascriptText (ti:/module.js:457:9)
V8Exception: Exception occurred at undefined:1: Uncaught SyntaxError: Unexpected token o in JSON at position 1

Note that "Unexpected token o" is an error message from json-parser bundled inside V8 which is bundled inside Appcelerator Ti. This particular error suggests that JSON.parse() was called with an object that is already something other than a JSON string, for example and already-parsed JSON object.

Here's a log from a different app:

TiExceptionHandler: (main) [560,560] ----- Titanium Javascript Runtime Error -----
TiExceptionHandler: (main) [0,560] - In undefined:1,2
TiExceptionHandler: (main) [1,561] - Message: Uncaught SyntaxError: Unexpected token o in JSON at position 1
TiExceptionHandler: (main) [0,561] - Source: [object TiBlob]
V8Exception: Exception occurred at undefined:1: Uncaught SyntaxError: Unexpected token o in JSON at position 1

All affected apps have in common that they call android.webkit.MimeTypeMap.getMimeTypeFromExtension("json"), which returns "application/json" on Android Q Beta. On earlier versions of Android, it returned null. Changing MimeTypeMap to the behavior from before Android Q fixes the problematic issues (app errors).

Here's an example call trace of how Appcelerator Ti's TiBlob.blobFromFile is calling MimeTypeMap.getMimeTypeFromExtension("json"); this triggers an unknown different code path later on which leads to the error.

android.webkit.MimeTypeMap.getMimeTypeFromExtension(MimeTypeMap.java:92)
at org.appcelerator.titanium.util.TiMimeTypeHelper.getMimeTypeFromFileExtension(TiMimeTypeHelper.java:39)
at org.appcelerator.titanium.util.TiMimeTypeHelper.getMimeType(TiMimeTypeHelper.java:73)
at org.appcelerator.titanium.util.TiMimeTypeHelper.getMimeType(TiMimeTypeHelper.java:30)
at org.appcelerator.titanium.TiBlob.blobFromFile(TiBlob.java:107)
at org.appcelerator.titanium.io.TiFile.read(TiFile.java:383)
at org.appcelerator.titanium.TiFileProxy.read(TiFileProxy.java:286)
at org.appcelerator.kroll.runtime.v8.V8Object.nativeCallProperty(Native Method)
at org.appcelerator.kroll.runtime.v8.V8Object.callProperty(V8Object.java:75)
at org.appcelerator.kroll.KrollProxy.handleMessage(KrollProxy.java:1210)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7141)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)

Here is another stacktrace (slightly different from TiFileProxy.read() upwards):

android.webkit.MimeTypeMap.getMimeTypeFromExtension(MimeTypeMap.java:92)
at org.appcelerator.titanium.util.TiMimeTypeHelper.getMimeTypeFromFileExtension(TiMimeTypeHelper.java:33)
at org.appcelerator.titanium.util.TiMimeTypeHelper.getMimeType(TiMimeTypeHelper.java:58)
at org.appcelerator.titanium.util.TiMimeTypeHelper.getMimeType(TiMimeTypeHelper.java:25)
at org.appcelerator.titanium.TiBlob.blobFromFile(TiBlob.java:113)
at org.appcelerator.titanium.io.TiResourceFile.read(TiResourceFile.java:121)
at org.appcelerator.titanium.TiFileProxy.read(TiFileProxy.java:257)
at org.appcelerator.kroll.runtime.v8.V8Object.nativeFireEvent(Native Method)
at org.appcelerator.kroll.runtime.v8.V8Object.fireEvent(V8Object.java:62)
at org.appcelerator.kroll.KrollProxy.doFireEvent(KrollProxy.java:936)
at org.appcelerator.kroll.KrollProxy.handleMessage(KrollProxy.java:1159)
at org.appcelerator.titanium.proxy.TiViewProxy.handleMessage(TiViewProxy.java:363)
at ti.modules.titanium.ui.widget.listview.ListViewProxy.handleMessage(ListViewProxy.java:322)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loop(Looper.java:214)
at org.appcelerator.kroll.KrollRuntime$KrollRuntimeThread.run(KrollRuntime.java:118)

Overall, I'm not sure where the buggy code is that does the wrong thing when a TiBlob's mimetype is "application/json" but that does the right thing when the mimetype is null. It might be somewhere Appcelerator Titanium, for example in module.js from the Appcelerator Ti's runtime library, or it might be in multiple apps. Either way, the fact that TiBlob.blobFromFile() depends on behavior that changes between Android versions is part of the problem:

[...]
public static TiBlob blobFromFile(TiBaseFile file, String mimeType) {
if (mimeType == null) {
mimeType = TiMimeTypeHelper.getMimeType(file.nativePath());
}

Feel free to respond here if you have any follow-on questions.

The devDependency commitizen was updated from 3.0.6 to 3.0.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

commitizen is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency danger was updated from 7.1.2 to 7.1.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

danger is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @commitlint/config-conventional was updated from 7.1.2 to 7.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@commitlint/config-conventional is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Ti SDK: 1.4.2
Ti version: 1.2.2
device SDK :4.0.2

can't display retina image

Describe the bug

• I tried to package my mobile app for the Android Play Store and used a previous keystore. This keystore has a "Keystore Password" that is 7 characters long and a "Key Alias" that is 5 characters long. The publishing gets to the end but then errors.

To Reproduce

1. Publish - Distribute - Android Play Store
2. Signing errors with the following:

[INFO] :   Writing unsigned apk: **omitted**
[INFO] :   Using MD5withRSA (weak) signature algorithm
[INFO] :   Signing apk: /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/bin/jarsigner "-sigalg" "MD5withRSA (weak)" "-digestalg" "SHA1" "-keystore" "/dev_keystore" "-storepass" "*******" "-signedjar" "Name.apk" "../app-unsigned.apk" "tidev"
[ERROR] :  Failed to sign apk:
[ERROR] :  jarsigner error: java.security.NoSuchAlgorithmException: unrecognized algorithm name: MD5withRSA (weak)

Expected behavior
Expected the app to be signed. I haven't had issues in the past.

Environment
Titanium SDK version: 7.5.1 GA
CLI version: 5.1.1

Logs:

[INFO] :   Writing unsigned apk: **omitted**
[INFO] :   Using MD5withRSA (weak) signature algorithm
[INFO] :   Signing apk: /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/bin/jarsigner "-sigalg" "MD5withRSA (weak)" "-digestalg" "SHA1" "-keystore" "/dev_keystore" "-storepass" "*******" "-signedjar" "Name.apk" "../app-unsigned.apk" "tidev"
[ERROR] :  Failed to sign apk:
[ERROR] :  jarsigner error: java.security.NoSuchAlgorithmException: unrecognized algorithm name: MD5withRSA (weak)

The devDependency webpack was updated from 4.29.6 to 4.30.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency rollup was updated from 1.4.1 to 1.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

would it be possible to have access to the hyperloop module sources? I am testing the very last version of titanium v8. but then hyperloop module work because it needs to be rebuilt with the latest krollv8 for it to work. sadly i can't do that without the sources.
I did not find the sources on github. is it closed source ?
thanks

The dependency node-titanium-sdk was updated from 1.0.3 to 1.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-titanium-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Describe the bug
bubbleParent property on view not working on latest SDK 7.4.0 GA (XCODE 10).

We have signature drawing panel inside of scrollview. To stop scrolling on outer scrollview while drawing , we have put bubbleParent="false" on signature drawing webview.
Until SDK 7.3.1 GA and XCODE 9.2 , signature drawing was working fine.
But with SDK 7.4.0 GA and XCODE 10, the outer scrollview is scrolling .
Attaching videos below - One working with SDK 7.3.1 and one broken with SDK 7.4.0

To Reproduce
Steps to reproduce the behavior, e.g.:

1. Build app on SDK 7.4.0
2. Try drawing a signature in white box
3. See entire page scrolls. Page shouldn't scroll while signing.

Expected behavior
As Sign widget has bubbleParent="false", scrolling should not happen on parent view. It works as expected on SDK 7.3.1 GA. But breaks on SDK 7.4.0 GA

Environment
Titanium SDK version: SDK 7.4.0 GA
CLI version: 7.0.6

Logs:
Videos attached.

Sign drawing scroll issue videos.zip

(Attach by dragging into this issue)

The devDependency rollup was updated from 1.3.2 to 1.3.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency reflect-metadata was updated from 0.1.12 to 0.1.13.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

reflect-metadata is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency xcode was updated from 1.0.0 to 1.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

xcode is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency danger was updated from 7.0.8 to 7.0.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

danger is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴