Post

Replies

Boosts

Views

Activity

Apple Configurator: How to verify complete eSIM profile removal after sanitization?
We are developing a mobile-device diagnostics and sanitization platform for iPhone refurbishment and resale. We need clarification about Apple-supported methods for verifying eSIM profile removal after sanitization. Environment and observations Apple Configurator for Mac and cfgutil. Previously tested cfgutil erase --esim on an authorized test iPhone. Available device properties included ICCID, ICCID2, IMEI, IMEI2, and cellular capability. We could not establish a complete, authoritative machine-readable inventory of installed eSIM profiles. Physical SIM information can complicate interpretation of cellular identifiers. Our concern is that requesting eSIM deletion does not, by itself, prove that every installed profile was removed. Questions Does cfgutil erase --esim remove all installed eSIM profiles, including inactive profiles, on supported iPhones? Is there a supported Apple API or command-line interface for enumerating installed eSIM profiles before and after sanitization? Can EID/eUICC identity and profile-level ICCIDs be obtained through a supported interface? What is Apple's recommended method for confirming removal of previously installed profiles? Is there an authoritative way to prove that no installed eSIM profiles remain? What sanitization verification method does Apple recommend for refurbishment and resale operations? We want to avoid claiming complete eSIM sanitization when the supporting evidence is insufficient. Any guidance from Apple engineers or developers familiar with eSIM management and Apple Configurator would be appreciated. Related Feedback Assistant report: FB25599099
0
0
127
1d
Apple Configurator 2.21: cfgutil GET returns valid JSON but exit code 1
We are developing a mobile-device diagnostics platform and are investigating unexpected behavior in Apple Configurator's cfgutil command-line tool. Environment MacBook Pro running macOS 26.7.1 Apple Configurator 2.21, cfgutil build 1003.4 Two authorized test iPhones connected simultaneously Read-only operations with explicit ECID targeting Observed issue We executed an explicitly targeted property read: cfgutil --ecid <TARGET_ECID> --format JSON --timeout 15 get deviceClass The captured results were: Valid JSON response. The Devices array contained only the selected iPhone. The selected device's Output contained a nonempty deviceClass value. The device-specific Output.Errors object was empty. Standard error was empty. The process nevertheless exited with status code 1. We observed substantially the same behavior on two different iPhones in separate controlled tests. For comparison, positive ECID-filtered list requests returned the selected device with exit code 0. Requests using an unknown ECID returned "no devices found" with exit code 1. Questions Is exit status 1 expected for a successful cfgutil get deviceClass operation in Apple Configurator 2.21? If JSON contains valid property data and no device-specific error, what is the authoritative method for determining command success? Does --ecid guarantee that a GET operation is confined to the selected device when multiple iPhones are connected? Is there a documented limitation involving iPhones in their initial setup state? Is there an Apple-supported alternative for reliable, read-only, exact-device identification and property retrieval? Reliable device targeting and unambiguous command results are essential for preventing cross-device attribution in our application. We have not retried the failed operations because the exit-code behavior is unexplained. Related Apple Feedback Assistant report: FB25599039 Any guidance from Apple engineers or developers familiar with Configurator's command-line behavior would be appreciated.
0
1
38
1d
Apple Configurator: How to verify complete eSIM profile removal after sanitization?
We are developing a mobile-device diagnostics and sanitization platform for iPhone refurbishment and resale. We need clarification about Apple-supported methods for verifying eSIM profile removal after sanitization. Environment and observations Apple Configurator for Mac and cfgutil. Previously tested cfgutil erase --esim on an authorized test iPhone. Available device properties included ICCID, ICCID2, IMEI, IMEI2, and cellular capability. We could not establish a complete, authoritative machine-readable inventory of installed eSIM profiles. Physical SIM information can complicate interpretation of cellular identifiers. Our concern is that requesting eSIM deletion does not, by itself, prove that every installed profile was removed. Questions Does cfgutil erase --esim remove all installed eSIM profiles, including inactive profiles, on supported iPhones? Is there a supported Apple API or command-line interface for enumerating installed eSIM profiles before and after sanitization? Can EID/eUICC identity and profile-level ICCIDs be obtained through a supported interface? What is Apple's recommended method for confirming removal of previously installed profiles? Is there an authoritative way to prove that no installed eSIM profiles remain? What sanitization verification method does Apple recommend for refurbishment and resale operations? We want to avoid claiming complete eSIM sanitization when the supporting evidence is insufficient. Any guidance from Apple engineers or developers familiar with eSIM management and Apple Configurator would be appreciated. Related Feedback Assistant report: FB25599099
Replies
0
Boosts
0
Views
127
Activity
1d
Apple Configurator 2.21: cfgutil GET returns valid JSON but exit code 1
We are developing a mobile-device diagnostics platform and are investigating unexpected behavior in Apple Configurator's cfgutil command-line tool. Environment MacBook Pro running macOS 26.7.1 Apple Configurator 2.21, cfgutil build 1003.4 Two authorized test iPhones connected simultaneously Read-only operations with explicit ECID targeting Observed issue We executed an explicitly targeted property read: cfgutil --ecid <TARGET_ECID> --format JSON --timeout 15 get deviceClass The captured results were: Valid JSON response. The Devices array contained only the selected iPhone. The selected device's Output contained a nonempty deviceClass value. The device-specific Output.Errors object was empty. Standard error was empty. The process nevertheless exited with status code 1. We observed substantially the same behavior on two different iPhones in separate controlled tests. For comparison, positive ECID-filtered list requests returned the selected device with exit code 0. Requests using an unknown ECID returned "no devices found" with exit code 1. Questions Is exit status 1 expected for a successful cfgutil get deviceClass operation in Apple Configurator 2.21? If JSON contains valid property data and no device-specific error, what is the authoritative method for determining command success? Does --ecid guarantee that a GET operation is confined to the selected device when multiple iPhones are connected? Is there a documented limitation involving iPhones in their initial setup state? Is there an Apple-supported alternative for reliable, read-only, exact-device identification and property retrieval? Reliable device targeting and unambiguous command results are essential for preventing cross-device attribution in our application. We have not retried the failed operations because the exit-code behavior is unexplained. Related Apple Feedback Assistant report: FB25599039 Any guidance from Apple engineers or developers familiar with Configurator's command-line behavior would be appreciated.
Replies
0
Boosts
1
Views
38
Activity
1d