Search results for

“iPhone 16 pro”

80,726 results found

Post

Replies

Boosts

Views

Activity

Reply to macOS 12.6 LightsOutManagement; address already in use
Hi, @Dominik_2 I'm a little late here but I'm having the same issue. Did you ever figure this out? I can't even get a 2019 Mac Pro to properly activate LOM and a 2023 Mac mini which gives me the same Address Already In Use error. Here's all my testing and info. Apple are you there??? Infrastructure: • Mac mini 2023 (M2, 10Gb Ethernet, MacMini.local, macOS 15.x Sequoia 15.7.4) — MicroMDM v1.13.1 • Mac Pro 2019 (MacPro7,1, Intel T2, MacPro.local, macOS 15.x Sequoia 15.7.5, T2 firmware 23P3120) • Both supervised via Automated Device Enrollment (DEP) through Apple Business Manager • Both enrolled: IsSupervised = 1, APNs working on both • Both are Controllers and Clients LOM Current State: Mac mini (Apple Silicon M2): • LOM profile installed ✓ • lom0 interface active ✓ • Port 55555 listening on * ✓ • LOMDeviceServerColsolidated path (Apple Silicon) ✓ • com.apple.AppleLOM.XPC active=1 ✓ • com.apple.AppleLOM.Watchdog active=1 ✓ • Mac Pro CAN reach mini's lom0 port 55555 — TCP connection es
6d
Custom Capacitor 6 plugin with SPM: "plugin is not implemented on ios" despite being compiled
Hi everyone, I'm building an iOS app using Capacitor 6 with Swift Package Manager (SPM). I have a custom native plugin (AppleIAPPlugin) for StoreKit 2 In-App Purchases that lives in the App target (not as an SPM package). Despite compiling successfully, the JavaScript bridge throws: AppleIAP plugin is not implemented on ios Setup AppleIAPPlugin.swift: swift import Foundation import Capacitor import StoreKit @objc(AppleIAPPlugin) public class AppleIAPPlugin: CAPPlugin, CAPBridgedPlugin { public let identifier = AppleIAPPlugin public let jsName = AppleIAP public let pluginMethods: [CAPPluginMethod] = [ CAPPluginMethod(name: getProducts, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: purchase, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: restorePurchases, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: getCurrentEntitlements, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: openManageSubscriptions, returnType: CAPPluginReturnPromise), ] @objc func getProducts(_ call
1
0
33
6d
Unable to Download Apps via TestFlight - "The requested app is not available or doesn't exist" Error
Hi everyone I recently build an app and deployed it through app store connect and testet it on TestFlight. Everything worked fine up until build 1.0.3. Since then I have not been able to install the app on my phone through TestFlight - even though build and submission runs through successfully on eas, expo and app store. I have tried deleting and reinstalling the TestFlight from my phone. removing and adding back myself as tester. checking logs and commits from the shift from build 1.0.3 to build 1.0.4. I can see I changed name and slug, so I tried removing the app from app store connect and added a new one with new build and submission. Ran through successfully but still could not install the app through TestFlight on my iPhone. I have also tried reaching out to Apple Developer Support, but I have not heard from them. Has anyone tried something similar?
7
0
514
6d
Week 7 of Pending Enrollment
I will keep posting this every week because I simply cannot wait anymore. 7 weeks of waiting is way too much. To me, it is absolute madness in 2026 to wait for months, especially when my passport/ID was successfully verified back in week 1 or 2. To make matters worse, I can't even call the support hotline because the phone option is unavailable and the email assistants only reply with the same automated templates. P.S. If by some miracle Apple Support reads this post or rather, this cry from the soul - and actually wants to help, I have already created two support tickets. Here are the case numbers: 20000109972460 20000109363371
1
0
75
6d
iPhone收不到PushKit推送
token:eb3b63ab94b136f6d25a86d48bb4b7ff20377e393f137cb4f43b17560112bf51 msgId:67d4c88d-61b1-4f51-df0b-2efa022fd672 机型:iPhone7 系统:iOS 15.8.3 问题描述:后端服务器调用苹果提供的pushKit推送API且已成功返回上述msgId,客户端App也已经实现对应的CallKit方法reportNewIncomingCall,但没有收到对应的推送,这是什么原因呢?
1
0
56
6d
Reply to Crashed: com.apple.CFNetwork.LoaderQ
0 libquic.dylib 0x36d84 quic_fc_service_pending_send_data + 360 1 libquic.dylib 0x3bcf0 __quic_conn_outbound_stopping_block_invoke_2 + 28 2 Network 0x23e428 nw_protocol_instance_access_flow_state + 136 3 libquic.dylib 0x3bcb8 __quic_conn_outbound_stopping_block_invoke + 744 4 libquic.dylib 0x3b754 quic_conn_outbound_stopping + 168 5 Network 0x3559b4 nw_protocol_implementation_finalize_output_frames(nw_protocol*, nw_frame_array_s*) + 576 6 Network 0x67308 nw_flow_service_writes(NWConcrete_nw_endpoint_handler*, NWConcrete_nw_endpoint_flow*, nw_flow_protocol*) + 5264 7 Network 0x58944 nw_endpoint_handler_add_write_request + 4860 8 Network 0x57880 nw_endpoint_handler_add_write_request + 568 9 Network 0x575a4 nw_connection_add_write_request_on_queue(NWConcrete_nw_connection*, NSObject*, bool) + 228 10 Network 0x5c314 nw_connection_async_if_needed + 76 11 Network 0x573c4 nw_connection_add_write_request(NWConcrete_nw_connection*, NSObject*) + 312 12 Network 0x56868 nw_connection_send + 516 13 CFNetwork 0x66b30 NWIOC
6d
Reply to Working Anti Virus - Apple Developer Account terminated
Hi, I read your post and it sounds like an incredibly tough situation. I’ve been through a Pending Termination Notice myself, so I truly understand how stressful this can be. I’d like to share my experience just in case it might be of some help. At this stage, it might be more effective to focus less on defending the anti-virus app’s innovation and more on protecting your developer account and your livelihood. In my own case, focusing on a few specific points in my appeal seemed to make a difference: Clarify your intent: Since the app was flagged as malicious, you might want to clearly explain that you had absolutely no intention of misleading users. While your personal situation (such as losing your source of income) is completely understandable, Apple’s review process is guideline-driven, so I think it might be more effective to keep the tone as professional as possible. Write a concrete preventative measure: I mentioned this in another thread recently, but I believe including a clear preventative
6d
Invalid parameter not satisfying: parentEnvironment != nil
Since the beta releases of iPadOS 26 we have been having some crashes about Invalid parameter not satisfying: parentEnvironment != nil We got to contact a couple of users and we found out that the crash appears when entering a screen in a UINavigationController with the iPad device connected to a Magic Keyboard. If the device is not connected to the keyboard then nothing happens and everything works ok. From our end we haven't managed to reproduce the crash so I am pasting part of the stacktrace if it can be of any help. 3 UIKitCore 0x19dfd2e14 -[_UIFocusContainerGuideFallbackItemsContainer initWithParentEnvironment:childItems:] + 224 (_UIFocusContainerGuideFallbackItemsContainer.m:23) 4 UIKitCore 0x19dae3108 -[_UIFocusContainerGuideImpl _searchForFocusRegionsInContext:] + 368 (_UIFocusGuideImpl.m:246) 5 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 6 UIKitCore 0x19db28900 -[_UIFocusMapSnapshot addRegionsInContainers:] + 160 (_UIFocusMapSnapshot.m:545)
11
0
747
6d
Trader Account - Phone Verification
Hello, I'm trying to enroll on the trader account program but after filling out the form, then entering the email verification code that was sent I don't ever receive the phone OTP code that I'm supposed to receive. I'm not from the US, my country code is +51 so I select that on the dial code combo-box then enter my number that is 9 digits long. However, I tried with a US phone from a friend and it works just fine, he does receive the confirmation code. How can I fix this? I already have an app stuck for over 1 week because of this. I've called apple support multiple times and they send me to send evidence via email which I have. They've told me it was scaled to the engineering them but of course that's gonna take a long while for it to be fixed. Has anyone encountered a similar problem? I believe there's gotta be a quirk or something in that form that will actually get the system to work.
5
0
1.4k
6d
Reply to Monitor mode capture broken with Wi-Fi 7 (M5 Pro MacBook Pro) on macOS 26 - worked previously on same OS with older hardware
[quote='881663022, adriangm20, /thread/818603?answerId=881663022#881663022, /profile/adriangm20'] I've identified and submitted [FB22295165 and FB22295685] [/quote] Thanks. [quote='881663022, adriangm20, /thread/818603?answerId=881663022#881663022, /profile/adriangm20'] the ability to capture Wi-Fi traffic and use apps that rely on it is one of the reasons many WLAN and IT professionals choose Macs. [/quote] Understood. I can’t make any promises here, but I have passed these comments on to the folks looking at this issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Core OS Tags:
6d
Monitor mode capture broken with Wi-Fi 7 (M5 Pro MacBook Pro) on macOS 26 - worked previously on same OS with older hardware
Platform: macOS 26.3.1, M5 Pro MacBook Pro Framework: CoreWLAN Affected applications: NetViews, Air Tool 2, and our own tooling — appears to be specific to the new Wi-Fi 7 hardware Hardware Card Type: chip id: 0x11 api 1.2 firmware [Rev 72.11.260 N1B1 devFused=0] phy [17.1.17.0], core80211 [324.10.260 N1_silicon_b] Firmware: Jan 27 2026 21:18:32 version XBS_BUILD_TAG GIT_DESCRIBE FWID chip id: 0x11 api 1.2 firmware [Rev 72.11.260 N1B1 devFused=0] phy [17.1.17.0], core80211 [324.10.260 N1_silicon_b] Driver: IO80211_driverkit-1540.16 IO80211_driverkit-1540.16 Jan 27 2026 Background Both issues described below were working correctly on macOS 26 with previous-generation hardware. The regression is specific to the Wi-Fi 7 card shipping in the M5 Pro MacBook Pro. This is not an OS regression — it is a hardware/driver/firmware compatibility issue with the new card under macOS 26. Issue 1: disassociate() + tcpdump/Wireshark -I no longer enters monitor mode Previously, the standard
5
0
189
6d
iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
I am unable to use my iPhone 17 Pro as a run destination in Xcode. The device appears at a low level, but CoreDevice / devicectl keeps reporting it as unavailable. Environment • Mac mini (Apple Silicon) • macOS 26.3 (Build 25D125) • iPhone 17 Pro • iOS 26.3 • Xcode 26.3 (Build 17C529) • Xcode 26.4 beta 2 (Build 17E5170d) Symptoms • The iPhone appears in Finder • On the iPhone, I tapped “Trust This Computer” • Developer Mode is enabled • Apple ID is added in Xcode Accounts • Team is configured in Signing & Capabilities • iOS Platform Support is installed • The device still does not become available as a run destination • Devices and Simulators does not show it in a usable state • xcrun devicectl list devices still shows unavailable Output of xcrun devicectl list devices Failed to load provisioning paramter list due to error: Error Domain=com.apple.dt.CoreDeviceError Code=1002 No provider was found. UserInfo={NSLocalizedDescription=No provider was found.
13
0
461
6d
Reply to macOS 12.6 LightsOutManagement; address already in use
Hi, @Dominik_2 I'm a little late here but I'm having the same issue. Did you ever figure this out? I can't even get a 2019 Mac Pro to properly activate LOM and a 2023 Mac mini which gives me the same Address Already In Use error. Here's all my testing and info. Apple are you there??? Infrastructure: • Mac mini 2023 (M2, 10Gb Ethernet, MacMini.local, macOS 15.x Sequoia 15.7.4) — MicroMDM v1.13.1 • Mac Pro 2019 (MacPro7,1, Intel T2, MacPro.local, macOS 15.x Sequoia 15.7.5, T2 firmware 23P3120) • Both supervised via Automated Device Enrollment (DEP) through Apple Business Manager • Both enrolled: IsSupervised = 1, APNs working on both • Both are Controllers and Clients LOM Current State: Mac mini (Apple Silicon M2): • LOM profile installed ✓ • lom0 interface active ✓ • Port 55555 listening on * ✓ • LOMDeviceServerColsolidated path (Apple Silicon) ✓ • com.apple.AppleLOM.XPC active=1 ✓ • com.apple.AppleLOM.Watchdog active=1 ✓ • Mac Pro CAN reach mini's lom0 port 55555 — TCP connection es
Replies
Boosts
Views
Activity
6d
Custom Capacitor 6 plugin with SPM: "plugin is not implemented on ios" despite being compiled
Hi everyone, I'm building an iOS app using Capacitor 6 with Swift Package Manager (SPM). I have a custom native plugin (AppleIAPPlugin) for StoreKit 2 In-App Purchases that lives in the App target (not as an SPM package). Despite compiling successfully, the JavaScript bridge throws: AppleIAP plugin is not implemented on ios Setup AppleIAPPlugin.swift: swift import Foundation import Capacitor import StoreKit @objc(AppleIAPPlugin) public class AppleIAPPlugin: CAPPlugin, CAPBridgedPlugin { public let identifier = AppleIAPPlugin public let jsName = AppleIAP public let pluginMethods: [CAPPluginMethod] = [ CAPPluginMethod(name: getProducts, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: purchase, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: restorePurchases, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: getCurrentEntitlements, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: openManageSubscriptions, returnType: CAPPluginReturnPromise), ] @objc func getProducts(_ call
Replies
1
Boosts
0
Views
33
Activity
6d
Unable to Download Apps via TestFlight - "The requested app is not available or doesn't exist" Error
Hi everyone I recently build an app and deployed it through app store connect and testet it on TestFlight. Everything worked fine up until build 1.0.3. Since then I have not been able to install the app on my phone through TestFlight - even though build and submission runs through successfully on eas, expo and app store. I have tried deleting and reinstalling the TestFlight from my phone. removing and adding back myself as tester. checking logs and commits from the shift from build 1.0.3 to build 1.0.4. I can see I changed name and slug, so I tried removing the app from app store connect and added a new one with new build and submission. Ran through successfully but still could not install the app through TestFlight on my iPhone. I have also tried reaching out to Apple Developer Support, but I have not heard from them. Has anyone tried something similar?
Replies
7
Boosts
0
Views
514
Activity
6d
Reply to Enrollment frustration
after speaking on the phone, a support guy manually kicked off the email that gave me a link to https://developer.apple.com/contact/file-upload/upload/select to upload my ID, which I think was the missing step in the process. dunno if it'll work after that or not, but
Replies
Boosts
Views
Activity
6d
Week 7 of Pending Enrollment
I will keep posting this every week because I simply cannot wait anymore. 7 weeks of waiting is way too much. To me, it is absolute madness in 2026 to wait for months, especially when my passport/ID was successfully verified back in week 1 or 2. To make matters worse, I can't even call the support hotline because the phone option is unavailable and the email assistants only reply with the same automated templates. P.S. If by some miracle Apple Support reads this post or rather, this cry from the soul - and actually wants to help, I have already created two support tickets. Here are the case numbers: 20000109972460 20000109363371
Replies
1
Boosts
0
Views
75
Activity
6d
iPhone收不到PushKit推送
token:eb3b63ab94b136f6d25a86d48bb4b7ff20377e393f137cb4f43b17560112bf51 msgId:67d4c88d-61b1-4f51-df0b-2efa022fd672 机型:iPhone7 系统:iOS 15.8.3 问题描述:后端服务器调用苹果提供的pushKit推送API且已成功返回上述msgId,客户端App也已经实现对应的CallKit方法reportNewIncomingCall,但没有收到对应的推送,这是什么原因呢?
Replies
1
Boosts
0
Views
56
Activity
6d
Reply to Crashed: com.apple.CFNetwork.LoaderQ
0 libquic.dylib 0x36d84 quic_fc_service_pending_send_data + 360 1 libquic.dylib 0x3bcf0 __quic_conn_outbound_stopping_block_invoke_2 + 28 2 Network 0x23e428 nw_protocol_instance_access_flow_state + 136 3 libquic.dylib 0x3bcb8 __quic_conn_outbound_stopping_block_invoke + 744 4 libquic.dylib 0x3b754 quic_conn_outbound_stopping + 168 5 Network 0x3559b4 nw_protocol_implementation_finalize_output_frames(nw_protocol*, nw_frame_array_s*) + 576 6 Network 0x67308 nw_flow_service_writes(NWConcrete_nw_endpoint_handler*, NWConcrete_nw_endpoint_flow*, nw_flow_protocol*) + 5264 7 Network 0x58944 nw_endpoint_handler_add_write_request + 4860 8 Network 0x57880 nw_endpoint_handler_add_write_request + 568 9 Network 0x575a4 nw_connection_add_write_request_on_queue(NWConcrete_nw_connection*, NSObject*, bool) + 228 10 Network 0x5c314 nw_connection_async_if_needed + 76 11 Network 0x573c4 nw_connection_add_write_request(NWConcrete_nw_connection*, NSObject*) + 312 12 Network 0x56868 nw_connection_send + 516 13 CFNetwork 0x66b30 NWIOC
Replies
Boosts
Views
Activity
6d
Reply to Working Anti Virus - Apple Developer Account terminated
Hi, I read your post and it sounds like an incredibly tough situation. I’ve been through a Pending Termination Notice myself, so I truly understand how stressful this can be. I’d like to share my experience just in case it might be of some help. At this stage, it might be more effective to focus less on defending the anti-virus app’s innovation and more on protecting your developer account and your livelihood. In my own case, focusing on a few specific points in my appeal seemed to make a difference: Clarify your intent: Since the app was flagged as malicious, you might want to clearly explain that you had absolutely no intention of misleading users. While your personal situation (such as losing your source of income) is completely understandable, Apple’s review process is guideline-driven, so I think it might be more effective to keep the tone as professional as possible. Write a concrete preventative measure: I mentioned this in another thread recently, but I believe including a clear preventative
Replies
Boosts
Views
Activity
6d
Invalid parameter not satisfying: parentEnvironment != nil
Since the beta releases of iPadOS 26 we have been having some crashes about Invalid parameter not satisfying: parentEnvironment != nil We got to contact a couple of users and we found out that the crash appears when entering a screen in a UINavigationController with the iPad device connected to a Magic Keyboard. If the device is not connected to the keyboard then nothing happens and everything works ok. From our end we haven't managed to reproduce the crash so I am pasting part of the stacktrace if it can be of any help. 3 UIKitCore 0x19dfd2e14 -[_UIFocusContainerGuideFallbackItemsContainer initWithParentEnvironment:childItems:] + 224 (_UIFocusContainerGuideFallbackItemsContainer.m:23) 4 UIKitCore 0x19dae3108 -[_UIFocusContainerGuideImpl _searchForFocusRegionsInContext:] + 368 (_UIFocusGuideImpl.m:246) 5 UIKitCore 0x19db28498 -[_UIFocusMapSnapshot addRegionsInContainer:] + 2720 (_UIFocusMapSnapshot.m:531) 6 UIKitCore 0x19db28900 -[_UIFocusMapSnapshot addRegionsInContainers:] + 160 (_UIFocusMapSnapshot.m:545)
Replies
11
Boosts
0
Views
747
Activity
6d
Trader Account - Phone Verification
Hello, I'm trying to enroll on the trader account program but after filling out the form, then entering the email verification code that was sent I don't ever receive the phone OTP code that I'm supposed to receive. I'm not from the US, my country code is +51 so I select that on the dial code combo-box then enter my number that is 9 digits long. However, I tried with a US phone from a friend and it works just fine, he does receive the confirmation code. How can I fix this? I already have an app stuck for over 1 week because of this. I've called apple support multiple times and they send me to send evidence via email which I have. They've told me it was scaled to the engineering them but of course that's gonna take a long while for it to be fixed. Has anyone encountered a similar problem? I believe there's gotta be a quirk or something in that form that will actually get the system to work.
Replies
5
Boosts
0
Views
1.4k
Activity
6d
Reply to Monitor mode capture broken with Wi-Fi 7 (M5 Pro MacBook Pro) on macOS 26 - worked previously on same OS with older hardware
[quote='881663022, adriangm20, /thread/818603?answerId=881663022#881663022, /profile/adriangm20'] I've identified and submitted [FB22295165 and FB22295685] [/quote] Thanks. [quote='881663022, adriangm20, /thread/818603?answerId=881663022#881663022, /profile/adriangm20'] the ability to capture Wi-Fi traffic and use apps that rely on it is one of the reasons many WLAN and IT professionals choose Macs. [/quote] Understood. I can’t make any promises here, but I have passed these comments on to the folks looking at this issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
6d
Monitor mode capture broken with Wi-Fi 7 (M5 Pro MacBook Pro) on macOS 26 - worked previously on same OS with older hardware
Platform: macOS 26.3.1, M5 Pro MacBook Pro Framework: CoreWLAN Affected applications: NetViews, Air Tool 2, and our own tooling — appears to be specific to the new Wi-Fi 7 hardware Hardware Card Type: chip id: 0x11 api 1.2 firmware [Rev 72.11.260 N1B1 devFused=0] phy [17.1.17.0], core80211 [324.10.260 N1_silicon_b] Firmware: Jan 27 2026 21:18:32 version XBS_BUILD_TAG GIT_DESCRIBE FWID chip id: 0x11 api 1.2 firmware [Rev 72.11.260 N1B1 devFused=0] phy [17.1.17.0], core80211 [324.10.260 N1_silicon_b] Driver: IO80211_driverkit-1540.16 IO80211_driverkit-1540.16 Jan 27 2026 Background Both issues described below were working correctly on macOS 26 with previous-generation hardware. The regression is specific to the Wi-Fi 7 card shipping in the M5 Pro MacBook Pro. This is not an OS regression — it is a hardware/driver/firmware compatibility issue with the new card under macOS 26. Issue 1: disassociate() + tcpdump/Wireshark -I no longer enters monitor mode Previously, the standard
Replies
5
Boosts
0
Views
189
Activity
6d
iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
I am unable to use my iPhone 17 Pro as a run destination in Xcode. The device appears at a low level, but CoreDevice / devicectl keeps reporting it as unavailable. Environment • Mac mini (Apple Silicon) • macOS 26.3 (Build 25D125) • iPhone 17 Pro • iOS 26.3 • Xcode 26.3 (Build 17C529) • Xcode 26.4 beta 2 (Build 17E5170d) Symptoms • The iPhone appears in Finder • On the iPhone, I tapped “Trust This Computer” • Developer Mode is enabled • Apple ID is added in Xcode Accounts • Team is configured in Signing & Capabilities • iOS Platform Support is installed • The device still does not become available as a run destination • Devices and Simulators does not show it in a usable state • xcrun devicectl list devices still shows unavailable Output of xcrun devicectl list devices Failed to load provisioning paramter list due to error: Error Domain=com.apple.dt.CoreDeviceError Code=1002 No provider was found. UserInfo={NSLocalizedDescription=No provider was found.
Replies
13
Boosts
0
Views
461
Activity
6d
Reply to iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
Have you solved it ? I am facing same issue with IPhone 14 (26.04) and Xcode (26.4). CoreDevice / devicectl layer the device remains unavailable, and Xcode cannot use it for on-device build/run.
Replies
Boosts
Views
Activity
6d
Reply to iCloud Sync not working with iPhone, works fine for Mac.
Just to add one more piece to this... Make a change on the Mac AppleTV makes the change instantly Apple Watch makes the change instantly iPhone only updates after you leave the app and launch it again iPad only updates after you leave the app and launch it again
Replies
Boosts
Views
Activity
6d