앱스토어 app 승인 기록

멀고도 먼 앱스토어 app 승인 기록을 남긴다.

▼	앱 심사  2023년 3월 22일 오후 10:05 Guideline 2.1 - Information Needed We have started your app's review, but we were unable to successfully access all or part of your app. In order for us to continue the review, we need to have a way to verify all app features and functionality. Typically this is done by providing a demo account that has access to all features and functionality in your app. Next Steps To resolve this issue, provide a user name and password in the App Review Information section of App Store Connect. It is also acceptable to include a demonstration mode that exhibits your app’s full features and functionality. Note that providing a demo video showing your app in use is not sufficient for us to continue the review. Resources - Watch a video from App Store Review with tips for preventing common rejections. - To learn more about providing information to App Store Review in App Store Connect, see App Store Connect Help. iOS 앱 1.0.3000 | 앱 버전 거절 사유: 2.1.0 Performance: App Completeness
▶	앱 실행을 위해서는 가입이 필수인데, 한국 전화번호 없이는 가입이 안되니 앱 사용하는 동영상으로 찍어서 보냈으나, 기능 테스트를 반드시 해야 한다는게 애플의 입장이다.  그래도 혹시 몰라서 다시 한번 보내봤다.
▼	나  2023년 3월 23일 오전 11:29 우리 앱을 사용하는데 있어서 한국의 통신사에 가입된 핸드폰 번호가 필수로 사용됩니다. 그리하여 앱의 사용성에 대해서 동영상을 첨부합니다. 메시지 첨부 파일: 230323.MP4
▼	앱 심사  2023년 3월 23일 오후 10:10 Hello, The issues we previously identified still need your attention. Guideline 2.1 - Information Needed We have started your app's review, but we were unable to successfully access all or part of your app. In order for us to continue the review, we need to have a way to verify all app features and functionality. Typically this is done by providing a demo account that has access to all features and functionality in your app. Next Steps To resolve this issue, provide a user name and password in the App Review Information section of App Store Connect. It is also acceptable to include a demonstration mode that exhibits your app’s full features and functionality. Note that providing a demo video showing your app in use is not sufficient for us to continue the review. Resources - Watch a video from App Store Review with tips for preventing common rejections. - To learn more about providing information to App Store Review in App Store Connect, see App Store Connect Help. iOS 앱 1.0.3000 | 앱 버전 거절 사유: 2.1.0 Performance: App Completeness
▶	결국은 가입없이도 사용할 수 있도록 기능을 추가해서 제공하기로 한다.
▼	나  2023년 3월 24일 오전 10:33 * [screenshot1] 데모 모드로 앱을 사용할 수 있습니다. [230324DemoMode] 데모모드로 들어가는 영상도 첨부합니다. * [230324] 데모모드라고 할지라도 이 앱은 한국의 지도만 사용하기 때문에 기타 기능은 사용할 수 없습니다. 그래서 사용영상도 첨부 합니다. * 우리 앱은 한국에서 개통된 전화번호 및 한국의 지도를 필수로 사용합니다. * 한국 이외의 국가에서 사용시 기능에 제한이 있습니다. 메시지 첨부 파일: screenshot1.png  230324DemoMode.MP4 230324.MP4
▼	앱 심사  2023년 3월 25일 오전 12:50 Guideline 2.3.8 - Performance - Accurate Metadata We noticed that the app name to be displayed on the App Store and the app name displayed on the device do not sufficiently match, which makes it difficult for users to find the app they just downloaded. The app names are: - Name on the App Store: XXXXX - Name displayed on the device: YYYYY Next Steps To resolve this issue, please change one or both names so they are more similar and the user can easily locate the app they just downloaded. It is important not to change your Bundle Identifier, which is used to uniquely identify your app in the App Store. Changing the Bundle Identifier will prevent users from upgrading and will effectively introduce a new app rather than an update. Resources For information on how to revise your device name, please review Technical Q&A QA1823: Updating the Display Name of Your App and Technical Q&A QA1892: Making the app name displayed on a device consistent with the name in iTunes Connect. For information on changing the app name and other metadata in App Store Connect, please review the View and edit app information section of App Store Connect Developer Help. For resources on selecting a memorable and unique app name, you may want to review the App Store Product Page information available on the Apple Developer website. iOS 앱 1.0.3000 | 앱 버전 거절 사유: 2.3.8 Performance: Accurate Metadata
▶	앱스토어에 올라가 있는 앱 이름과 info.plist의 이름이 달라서 안된다고...
▼	나  2023년 3월 27일 오전 09:29 Name on the App Store에 Name displayed on the device의 내용을 반영하여 다시 제출합니다.
▼	앱 심사  2023년 3월 27일 오후 11:28 Hello, Thank you for your resubmission. Upon further review, we identified an additional issue that needs your attention. See below for more information. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Bug Fix Submissions The issues we've identified below are eligible to be resolved on your next update. If this submission includes bug fixes and you'd like to have it approved at this time, reply to this message and let us know. You do not need to resubmit your app for us to proceed. Alternatively, if you'd like to resolve these issues now, please review the details, make the appropriate changes, and resubmit. Guideline 2.1 - Performance - App Completeness We discovered one or more bugs in your app. Specifically, the account deletion button in Profile was unresponsive when we tapped. Please review the details below and complete the next steps. Review device details: - Device type: iPad - OS version: iOS 16.3.1 Next Steps Please run your app on a device to reproduce the issues, then revise and submit your app for review. If at first you're unable to reproduce the issue, try the following: - For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce. - For app updates, install the new version as an update to the previous version, then follow the steps to reproduce. If we misunderstood the intended behavior of your app, please reply to this message in App Store Connect to provide information on how these features were intended to work. Resources - For information about testing apps and preparing them for review, see Testing a Release Build. - To learn about troubleshooting networking issues, see About Networking. - Watch a video from App Store Review with tips for preventing common rejections. Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requests the user’s consent to access the camera, but doesn’t sufficiently explain the use of the camera in the purpose string. To help users make informed decisions about how their data is used, permission request alerts need to explain and include an example of how your app will use the requested information. Next Steps Please revise the purpose string in your app’s Info.plist file for the camera to explain why your app needs access and include an example of how the user's data will be used. You can modify your app's Info.plist file using the property list editor in Xcode. Resources - Watch a video from App Store Review with tips for writing clear purpose strings. - See examples of helpful, informative purpose strings. - Review a list of relevant property list keys. Please see attached screenshots for details. iOS 앱 1.0.3000 | 앱 버전 거절 사유: 2.1.0 Performance: App Completeness 5.1.1 Legal: Privacy - Data Collection and Storage 거절 첨부 파일: Screenshot-0327-152658.png Screenshot-0327-152719.png
▶	카메라 권한 요청할때 왜 이 권한이 필요한지, 그리고 획득한 권한으로 무엇을 할지 상세 내용을 Info.plist에 추가하란다.
▼	나  2023년 3월 28일 오후 06:10 * 카메라 권한 요청에 대해 상세한 내용을 추가하였습니다. * 리포트 받은 버그를 수정하였습니다.
▼	앱 심사  2023년 3월 29일 오전 3:31 Hello, Thank you for your efforts to follow our guidelines. There are still some issues that need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Guideline 2.1 - Performance - App Completeness We're looking forward to completing our review, but we are unable to continue because your app crashed during review. Please review the details below and the attached crash logs, then complete the next steps. Steps leading to crash: - Crashes when as soon as we access test mode Review device details: - Device type: iPhone - OS version: iOS 16.3.1 Next Steps 1. Fully symbolicate the crash report. See Adding Identifiable Symbol Names to a Crash Report. 2. Match the crash report to a common pattern. Based on the pattern, take specific actions to further investigate the crash. See Identifying the Cause of Common Crashes. 3. Once you've identified the root causes of the crash, make the appropriate changes to the binary to resolve the issue. 4. Test your app on a device to ensure that it runs as expected. 5. Create and submit a new build for review. Resources - For more information on crash reports, see Diagnosing Issues Using Crash Reports and Device Logs. - To learn about troubleshooting networking issues, see About Networking. iOS 앱 1.0.3000 | 앱 버전 거절 사유: 2.1.0 Performance: App Completeness 거절 첨부 파일: crashlog-14053370-DCD0-43CD-B404-D213C13B8AB5.txt crashlog-5E80111B-0373-460C-810D-1D3E6B05538B.txt
▶	앱크래쉬가 발생했하고 한다. 크래쉬 파일은 다음과 같이 작업해서 확인한다. 1. Xcode 실행 2. Windows > Device & Simulators 실행 3. Device & Simulators에서 기기 선택 후 View Debug Logs 버튼 클릭 4. 크래쉬 파일을 넣으면 심볼릭된 로그를 확인할 수 있다. 재현이 되지 않아서 혹시 몰라 그냥 다시 심사 진행한다.
▼	앱 심사 2023년 3월 31일 오전 2:37 Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Guideline 2.1 - Performance - App Completeness We're looking forward to completing our review, but we are unable to continue because your app crashed during review. Please review the details below and the attached crash logs, then complete the next steps. Steps leading to crash: - Crashes when accessing menu (top left) on test mode Review device details: - Device type: iPhone - OS version: iOS 16.4 Next Steps 1. Fully symbolicate the crash report. See Adding Identifiable Symbol Names to a Crash Report. 2. Match the crash report to a common pattern. Based on the pattern, take specific actions to further investigate the crash. See Identifying the Cause of Common Crashes. 3. Once you've identified the root causes of the crash, make the appropriate changes to the binary to resolve the issue. 4. Test your app on a device to ensure that it runs as expected. 5. Create and submit a new build for review. Resources - For more information on crash reports, see Diagnosing Issues Using Crash Reports and Device Logs. - To learn about troubleshooting networking issues, see About Networking. iOS 앱 1.0.3000 | 앱 버전 거절 사유: 2.1.0 Performance: App Completeness 거절 첨부 파일: crashlog-C8791242-80E5-4DC1-8CFB-195DFEE22C44.txt crashlog-C8791242-80E5-4DC1-8CFB-195DFEE22C44 1.txt crashlog-C4EBA3AA-3CFB-4965-BC46-7571B16233B1.txt
▶	재현은 되지 않고 결국은 의심되는 부분을 수정해서 제출해 본다.
▼	나 2023년 3월 31일 오후 2:01 Hello. I still could not reproduce about reported issues. So I have modified codes by my guess but I can not confirm isseu is solved. I submitted the updated version(21). Please check it out. Thanks.
▼	앱 심사 2023년 3월 31일 오후 10:31 Hello, Thank you for your resubmission. Upon further review, we identified an additional issue that needs your attention. See below for more information. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Bug Fix Submissions The issues we've identified below are eligible to be resolved on your next update. If this submission includes bug fixes and you'd like to have it approved at this time, reply to this message and let us know. You do not need to resubmit your app for us to proceed. Alternatively, if you'd like to resolve these issues now, please review the details, make the appropriate changes, and resubmit. Guideline 2.1 - Performance - App Completeness We discovered one or more bugs in your app. - Specifically, your app displayed an error message when we tapped on ‘문의 접수.’ Review device details: - Device type: iPad - OS version: iOS 16.4 Next Steps Please run your app on a device to reproduce the issues, then revise and submit your app for review. If at first you're unable to reproduce the issue, try the following: - For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce. - For app updates, install the new version as an update to the previous version, then follow the steps to reproduce. If we misunderstood the intended behavior of your app, please reply to this message in App Store Connect to provide information on how these features were intended to work. Resources - For information about testing apps and preparing them for review, see Testing a Release Build. - To learn about troubleshooting networking issues, see About Networking. - Watch a video from App Store Review with tips for preventing common rejections. Please see attached screenshot for details. iOS 앱 1.0.3000 | 앱 버전 거절 사유: 2.1.0 Performance: App Completeness 거절 첨부 파일: Screenshot-0331-062943.png
▶	서버오류라는 메시지가 발생한다고 한다.  예상되는건 미국에서 테스트 하는 거라 GPS나, 네트워크 응답속도가 문제일것 같다. GPS 위치도 강제로 바꿔보고 VPN 써서 네트워크 속도도 다운시켰지만 이번에도 재현이 안된다. ㅠㅠ 그러다가 우연하게 iOS의 설정에 개발자라는 항목이 있는데 여기서 네트워크 속도를 제한할 수 있는 것을 확인했다. 설정 > 개발자 > Network Link Conditioner > Enable 'ON' & Very Bad Network 선택 우와! 바로 재현이 된다. GoogleServices-Info.plist 의 키가 잘못된거였다. 제대로 된 키의 GoogleServices-Info.plist로 교체 해서 문제를 해결한다.
▼	나 2023년 4월 3일 오전 10:37 Hello. We fixed the reported bug. The testmode user is not officially joined member. So you cannot register "문의접수". And cannot add a credit card & call a taxi. Please understand.

 

마침내 승인 통과 메일을 받게 되어 출시 한다.

 

앱 출시 참 어렵네.