material-components / material-components/material-components-android
[MaterialContainerTransform] Device gets paused temporarily when finishing an activity.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.4k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
#### [Description]
Device gets paused temporarily when finishing an activity after returned from container transform.
#### [Affected Dependency]
`1.3.0-alpha01`, `1.3.0-alpha02`.
Previous dependencies are working properly.
#### 1.2.0-alpha06

#### 1.3.0-alpha01, 1.3.0-alpha02

#### [Affected Devices]
Samsung Galaxy s10, Samsung Galaxy s7, Nexus 10, Pixel 2.
#### [Source code repository]
This [repository](https://github.com/skydoves/transformationlayout) using material `1.3.0-alpha02` dependency.
We can test `1.2.0-alpha06` version by resetting commits.
```gradle
git reset --hard 54b792b
```
Working properly - [54b792b](https://github.com/skydoves/TransformationLayout/commit/54b792b6f9f2eb9054c5cbba5de8149360cad697)
Issue occur since this commit - [89fa4ed](https://github.com/skydoves/TransformationLayout/commit/89fa4ed666ba2b01730cf10bedca3deb1453a7dc)
#### [Gradle Build Tool Version]
`3.6.3` ~ `4.0.1`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked TransformationLayout repository and compare commit 54b792b, which works, with 89fa4ed, where the issue begins. Reproduce the activity finish flow using Material 1.3.0-alpha01 or alpha02, then compare it with 1.2.0-alpha06 across the listed devices. Done means finishing an activity after returning from the container transform no longer temporarily pauses the device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100