非觸式e-‪道‬ 4+

Name: 非觸式e-道
Rating: 2.3 (351 reviews)
Author: Hong Kong Immigration Department

Hong Kong Immigration Department

專為 iPhone 設計

- 2.3 • 351 個評分

- 免費

iPhone 螢幕截圖

描述

非觸式e-道流動應用程式讓合資格的香港居民登記使用非觸式e-道服務。完成登記後，市民只需要利用他們的個人流動電話產生的加密e-道二維碼進入非觸式e-道內，並在標示的位置望向鏡頭，讓系統核實其容貌便可辦理出入境手續，過程中不用接觸共用的指紋掃描器。

非觸式e-道能讓市民在自助辦理出入境手續時，減少接觸共用設備，帶來更快捷、方便及衞生的出入境服務。

透過非觸式e-道流動應用程式登記使用非觸式e-道服務：
● 使用已啟用生物特徵認證的個人流動裝置，下載並安裝e-道流動應用程式及「智方便 iAM Smart」流動應用程式
● 登記及啟用「智方便」
● 開啟非觸式e-道流動應用程式及選擇登記服務
● 閱讀聲明及提交登記後，系統會透過「智方便」驗證其身分
● 通過身分驗證後，再提供與流動電話的內置生物認證以完成登記程序
● 完成登記後，申請人便可透過非觸式e-道流動應用程式產生的e-道二維碼於非觸式e-道辦理出入境手續

注意事項:
● 11至17歲之人士必須在父母或監護人的同意下進行登記。
● 由於使用非觸式e-道流動應用程式須經手機傳送數據，故用戶可能須繳付數據傳輸費用。流動數據用戶應留意所使用的數據用量。

2024年7月18日

版本 1.0.10

效能提升及改善應用程式

2.3 滿分 5 粒星

351 個評分

Screen brightness not restored after App closed

It is understandable that the App turn the screen brightness to maximum for better experience with the scanner. However, please restore the screen brightness to the level before the App started. It is very annoying that I have to turn my screen brightness down after every use of the App. This is easy to fix and don’t expect to see this bug again in the next release.

E1003 error and the app crashed

I’m using iPhone 13pro max. Opened the app and crashed immediately saying e1003 (my device isn’t supported by the app). iOS 16.5 still couldn’t work. I’ve restarted my phone but the problem persists. My friend uses the same model of iPhone and he can use the app without problem - and that helps me rule out possible hardware issue. At last, I removed apps that I seldom use and the crash problem no longer exists. Hope that helps you guy fix the issue and use the app before new version rolls out!

登記唔到呀！！

㩒完智方便就彈呢句野

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.