[BUG]: libwebcrypto.so isn't 16 KB page aligned
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 52/100
研究方向
Start with mobile/pubspec.lock to trace the webcrypto, webpush_encryption, and unifiedpush versions, then inspect .github/workflows/android-release.yaml for the Android build checks. Check libwebcrypto.so with readelf -lW and test loading or push decryption on the 16 KB Android emulator. Done means its PT_LOAD alignment is at least 0x4000 and CI checks every .so.
由索引模型根據 Issue 內容生成。
描述
Context
Android devices with 16 KB memory pages (some Android 15+ devices, and the 16 KB emulator images) can only load native libraries whose ELF LOAD segments are aligned to at least 16 KB.
Checking a release APK built from main (arm64-v8a):
| Library | LOAD alignment |
|---|---|
| libapp.so, libflutter.so | 64 KB |
| libdartjni.so, libdatastore_shared_counter.so, libsqlcipher.so | 16 KB |
| libwebcrypto.so | 4 KB |
The zip alignment (zipalign -c -P 16) passes; only libwebcrypto.so fails. It comes from webcrypto 0.6.0, pulled in by unifiedpush → webpush_encryption, so it is new with push notifications (#204).
What to do
- Find out when
libwebcrypto.sois loaded (at start-up, or only when a push message is decrypted) and what happens on a 16 KB device: crash, or notifications silently failing. - Try
webcrypto 0.6.1(the latest) and check its alignment; otherwise look at a newerwebpush_encryption/unifiedpush, or report it upstream. - Add an alignment check for every
.soto CI, so this can't come back unnoticed.
Where to look
mobile/pubspec.lock (webcrypto, webpush_encryption), .github/workflows/android-release.yaml.
Good to know
To check a library: read the p_align of its PT_LOAD program headers (readelf -lW lib.so); it must be 0x4000 or more. Test on the "16 KB page size" Android emulator image.
- 主要語言
- Dart
- 星號
- 9
- 分支
- 5
- 平均合併
- 49 分鐘
- 30 天內合併 PR
- 34
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
CommandLineCoding/Elephant 的其他 Issue
-
area: mobile chore good first issue
難度 2/5 1-3 小時 新手友好度 76/100
CommandLineCoding/Elephant#247 ·
維護者通常 1 天內回覆
-
area: mobile bug good first issue
難度 2/5 1-3 小時 新手友好度 88/100
CommandLineCoding/Elephant#245 ·
維護者通常 1 天內回覆
-
area: mobile enhancement good first issue
難度 2/5 1-3 小時 新手友好度 88/100
CommandLineCoding/Elephant#183 ·
維護者通常 1 天內回覆
-
area: mobile difficulty: medium enhancement
難度 4/5 3-5 天 新手友好度 56/100
CommandLineCoding/Elephant#249 ·
維護者通常 1 天內回覆
-
area: mobile chore difficulty: medium testing
難度 4/5 3-5 天 新手友好度 66/100
CommandLineCoding/Elephant#248 ·
維護者通常 1 天內回覆
查看 CommandLineCoding/Elephant 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 76/100
livekit/client-sdk-flutter#1281 ·
維護者通常 4 天內回覆
-
android bug priority: P1 qa
難度 2/5 1-3 小時 新手友好度 72/100
GHRik/bielik_oneclick_launcher#55 ·
維護者通常 1 天內回覆
-
SchedulerBinding.requestPerformanceMode(mode) does not forward the requested mode to the engine.未關閉
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
carp demo apps enhancement
難度 2/5 1-3 小時 新手友好度 78/100
carp-dk/carp.sensing-flutter#670 ·
-
難度 2/5 1-3 小時 新手友好度 78/100