Fixed
Status Update
Comments
xa...@android.com <xa...@android.com> #2
Thank you for this feedback. The team may reach out for more information on triaging or reproducing this issue.
[Deleted User] <[Deleted User]> #3
pallavi@ - Have we done any testing on Win7? Looks like this issue should be easily reproducible.
je...@google.com <je...@google.com>
hu...@gmail.com <hu...@gmail.com> #4
a.sworowska: could you click the "view problem details" button and send us what that shows?
zyy: is there any other useful information about a crash on Windows that's easily available?
zyy: is there any other useful information about a crash on Windows that's easily available?
cu...@gmail.com <cu...@gmail.com> #5
Problem signature:
Problem Event Name: APPCRASH
Application Name: adb.exe
Application Version: 0.0.0.0
Application Timestamp: 34f534d5
Fault Module Name: adb.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 34f534d5
Exception Code: 40000015
Exception Offset: 00016717
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 7763
Additional Information 2: 7763cd91f17ba1394e15130ad28436a8
Additional Information 3: 622c
Additional Information 4: 622c3aed538ac58f09882fe423edc57a
Also there's a console output: (for adb devices)
List of devices attached
* daemon not running. starting it now at tcp:5037 *
error: cannot open transport registration socketpair: Input/output error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Problem Event Name: APPCRASH
Application Name: adb.exe
Application Version: 0.0.0.0
Application Timestamp: 34f534d5
Fault Module Name: adb.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 34f534d5
Exception Code: 40000015
Exception Offset: 00016717
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 7763
Additional Information 2: 7763cd91f17ba1394e15130ad28436a8
Additional Information 3: 622c
Additional Information 4: 622c3aed538ac58f09882fe423edc57a
Also there's a console output: (for adb devices)
List of devices attached
* daemon not running. starting it now at tcp:5037 *
error: cannot open transport registration socketpair: Input/output error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
ch...@google.com <ch...@google.com>
jo...@google.com <jo...@google.com>
xa...@google.com <xa...@google.com>
hu...@google.com <hu...@google.com> #6
We have the same problem at my workplace (computers running with the same configuration).
Changing the port (5037) didn't solve.
We were thinking about a conflict with the company's proxy but we gave up to find a solution as soon as we downgrade to 25.0.3 and understood that the update was responsible of the crash.
Changing the port (5037) didn't solve.
We were thinking about a conflict with the company's proxy but we gave up to find a solution as soon as we downgrade to 25.0.3 and understood that the update was responsible of the crash.
je...@google.com <je...@google.com>
hm...@google.com <hm...@google.com> #7
>zyy: is there any other useful information about a crash on Windows that's easily available?
One can generate a minidump file on crash, here's instructions (WER part):https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/
Other option would be to integrate Breakpad (https://chromium.googlesource.com/breakpad/breakpad/ ); it will take much longer but would allow for automatic / user-initiated crash information submission
One can generate a minidump file on crash, here's instructions (WER part):
Other option would be to integrate Breakpad (
Description
Android gradle plugin version: 0.13.1
OS: MacOS
STEPS TO REPRODUCE:
1. Add a string to res/values/strings.xml
e.g. <string name="app_name">SimpleTest</string>
2. Add a product flavor which overrides this string:
productFlavors {
INT {
resValue "string", "app_name", "SimpleTest INT"
}
}
3. Execute:
gradle assembleINTDebug
EXPECTED RESULTS:
Build succeeds and the app is named "SimpleTest INT"
OBSERVED RESULTS:
Build fails with error:
:SimpleTest:mergeINTDebugResources FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':SimpleTest:mergeINTDebugResources'.
> /Users/xyz/AndroidStudioProjects/SimpleTest/SimpleTest/build/generated/res/generated/INT/debug/values/generated.xml: Error: Duplicate resources: /Users/xyz/AndroidStudioProjects/SimpleTest/SimpleTest/build/generated/res/generated/INT/debug/values/generated.xml:string/app_name, /Users/xyz/AndroidStudioProjects/SimpleTest/SimpleTest/src/main/res/values/strings.xml:string/app_name
ADDITIONAL INFORMATION:
When I add a resource file via a sourceSet for this build flavor instead of using resValue, I can successfully override the app_name.
I think setting a resource with resValue should behave the same as when using a sourceSet.