Fix Flutter transaction anomaly detection request handling
還沒有人認領這個 Issue。
評估
研究方向
查看 Flutter 應用的 pubspec.yaml 檔案，確保其中列出了 http 套件。找到包含 'import "http" as http;' 導入語句的檔案，將其更改為 'import "package:http/http.dart" as http;'。然後，找到交易異常偵測請求函數，為其新增針對非 2xx 回應、網路錯誤和 JSON 解析的錯誤處理。確保 API 基礎 URL 是可設定的，或許可以透過環境變數或設定檔實現。透過執行應用並模擬 API 故障來進行測試。
由索引模型根據 Issue 內容生成。
描述
Short summary
Flutter transaction anomaly detection request fails to compile and cannot be reliably exercised because the HTTP client import is invalid and request failures are not handled.
Affected version or release
Not specified in the source report; the affected application is a Flutter app using a development API endpoint.
Installation context
Flutter application using the AI Shield India transaction flow; requests target the development API endpoint at 10.0.2.2:8000.
What happened?
The Flutter application imports the HTTP client as import 'http' as http;, but the code calls http.post. This import does not reference the package library and prevents the app from compiling unless corrected to import 'package:http/http.dart' as http; and the http dependency is declared in pubspec.yaml. After compilation is fixed, the transaction flow should handle non-2xx responses, network and timeout failures, and invalid JSON without crashing. The API base URL should also be configurable for emulator, device, and production environments.
Steps to reproduce
- Create or open the Flutter application containing the AI Shield transaction flow.
- Ensure the code contains the HTTP import
import 'http' as http;and callshttp.post. - Run the application or compile the project.
- After correcting the import, invoke the Test High-Value Transfer action with the development API unavailable or returning an error.
- Observe the compilation failure or unhandled request/JSON failure.
Expected behavior
The app should compile with the HTTP package configured, send the transaction request successfully when the API is available, and show a user-friendly error when the API returns a non-2xx response, times out, cannot be reached, or returns invalid JSON. The API base URL should be configurable per environment.
Additional context
The original implementation uses http://10.0.2.2:8000/api/v1/detect-anomaly, which is emulator-specific and uses cleartext HTTP. Confirm the Android network-security configuration or migrate the endpoint to HTTPS. The request includes user ID, amount, current and previous locations, and screen-sharing state.
- 主要語言
- 沒有語言資料
- 星號
- 2.2k
- 分支
- 183
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/app 的其他 Issue
-
triage
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 85/100
-
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 62/100
相似的 Issue
-
enhancement
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
bisq-network/bisq-mobile#1948 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
streetcomplete/StreetComplete#7286 · 2 則留言 ·
維護者通常 1 天內回覆
-
bug-pending-triage
難度 2/5 1-3 小時 新手友好度 70/100
NativeScript/NativeScript#11525 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
callstack/agent-device#3627 ·
維護者通常 1 天內回覆