-
Notifications
You must be signed in to change notification settings - Fork 0
chore: Android Target SDK 36 대응 #252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
easyhooon
wants to merge
4
commits into
develop
Choose a base branch
from
BOOK-487-chore/#248
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
76ce237
[BOOK-487] chore: targetSdk 35 -> 36 upgrade
easyhooon 4b8264e
[BOOK-487] refactor: circuit 버전 업데이트 및 변경 사항 반영
easyhooon 1dd8263
[BOOK-487] chore: 라이브러리 버전 최신화
easyhooon 52dd7bd
Merge remote-tracking branch 'origin/develop' into BOOK-487-chore/#248
easyhooon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: YAPP-Github/Reed-Android
Length of output: 50
🏁 Script executed:
cat -n gradle/libs.versions.toml | head -60Repository: YAPP-Github/Reed-Android
Length of output: 1531
🌐 Web query:
Android SDK 36 portrait orientation warning issue💡 Result:
Short answer: This is expected with Android SDK 36 (Android 16). Apps targeting SDK 36 will have manifest orientation/resize restrictions ignored on large screens (sw600dp and up), so a portrait-locked app can be forced into other orientations or resizable windows on tablets/foldables/Chromebooks. You can either make your UI adaptive, opt out temporarily for compatibility, or limit distribution. (googblogs.com)
What to do (concise):
(Note: opt-out will be ignored for sw>=600dp starting API 37). (stackoverflow.com)
If you want, I can: show the exact manifest snippet, checklist for adapting layouts, or help test with Android 16 emulator images.
Citations:
🏁 Script executed:
Repository: YAPP-Github/Reed-Android
Length of output: 146
🏁 Script executed:
rg -i "screenorientation|PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY|supports-screens" --type xmlRepository: YAPP-Github/Reed-Android
Length of output: 158
🏁 Script executed:
rg "screenOrientation|PROPERTY_COMPAT" -A 2 -B 2Repository: YAPP-Github/Reed-Android
Length of output: 514
SDK 36 업그레이드는 portrait 화면 고정 관련 주요 변경사항이 필요합니다.
Android SDK 36 (Android 16)에서 portrait로 고정된 앱은 큰 화면(sw600dp 이상)에서 강제로 landscape 또는 resizable 상태로 변경됩니다. 현재
feature/main/src/main/AndroidManifest.xml의 MainActivity에android:screenOrientation="portrait"설정이 있으나, 이에 대한 완화 조치가 없습니다.다음 중 하나를 구현하세요:
<property android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY" android:value="true" />🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
이게 가능해? 현재 play console에서 지원하는지 궁금해
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
💡 Result:
Short answer
What that means (concise)
If you want, I can:
Sources
@easyhooon네, 가능합니다! Play Console에서 Device catalog 기능을 통해 특정 기기나 화면 크기별로 앱 배포를 제한할 수 있습니다.Play Console의 Device catalog에서 특정 모델을 수동으로 제외하거나 하드웨어 사양/성능 규칙으로 필터링할 수 있습니다.
실제 구현 방법:
Play Console Device catalog 사용 (권장):
Manifest의
<compatible-screens>(비권장):다만 주의사항:
Android 16부터 큰 화면(sw600dp 이상) 기기에서는 앱의 orientation/resizability 제한이 플랫폼 수준에서 무시되며, Google의 2026년 target SDK 정책으로 인해 많은 앱에 영향을 줄 예정입니다.
권장 사항:
기기 제한보다는 반응형 UI 구현이 장기적으로 더 나은 선택입니다. Google의 방향성이 앱을 adaptive하게 만드는 것이므로, 현재 portrait 고정을 유지하면서 점진적으로 landscape 지원을 추가하는 것을 고려해보세요.
필요하시면 Play Console의 Device catalog 설정 방법이나 반응형 UI 구현 가이드를 더 자세히 안내해드릴 수 있습니다! 🐰
(. .)
( づ💡
🧠 Learnings used