Search results for

“build disappears”

51,301 results found

Post

Replies

Boosts

Views

Activity

TestFlight build visible on macOS but not installable: “Can only be tested on an iOS device” for Mac (Designed for iPad)
Hello everyone. We have an app that has been on the App Store for several years, originally distributed for iOS and iPadOS only. Recently, we enabled Mac (Designed for iPad) and started distributing macOS-compatible builds. Current situation: The app is available and downloadable from the macOS App Store and runs correctly on Apple Silicon Macs. The same app/build appears in TestFlight on macOS, but cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatible, but TestFlight is treating the build as iOS-only. Environment and checks performed: Mac is Apple Silicon. App Store Connect app-level availability for Mac (Designed for iPad) is enabled. The app is not Mac Catalyst; it is a UIKit iOS/iPadOS app. Distribution is done via GitLab CI. CI uploads use an App Store provisioning profile (Apple Distribution), not development or ad-hoc. iPhone and iPad TestFlight installs work as expected. Info.plist ve
1
0
166
1w
Xcode 26 Warning: (arm64) empty dSYM file detected despite correct build settings
Hi Guys, Hope you're well! I am consistently encountering a build warning in Xcode 26 that prevents proper symbolication of crash logs. The warning states: warning: (arm64) /Users/mickey/Library/Developer/Xcode/DerivedData/CalendarSync-bjuvwxojzofqzzcmzzpdozbujrge/Build/Products/Debug-iphoneos/CalendarSync.app/CalendarSync empty dSYM file detected, dSYM was created with an executable with no debug info. Steps to Reproduce: Open the project in Xcode 26. Build the project for a physical iOS device (arm64) or Archive the project. The warning appears during the Generate dSYM phase of the build process. Troubleshooting Steps Already Taken (Issue Persists): Set 'Enable Debug Dylib Support' to No. Verified 'Debug Information Format' is set to 'DWARF with dSYM File'. Verified 'Generate Debug Symbols' is set to Yes. Set 'Strip Debug Symbols During Copy' and 'Strip Linked Product' to No. Performed 'Clean Build Folder' and manually deleted the DerivedData folder. The issue pe
2
0
74
1w
Attached macro loses generated source file
I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. Environment: Xcode 26.4 RC (17E192, latest); I believe it is also reproducible on earlier versions. github source code I reduced this to a very small macOS/iOS app plus a local macro package. The app logic is trivial, but app exits immediately on launch with code 138 Important observations: If I inline everything into a single file, the problem disappears. I also see an error like this during investigation: The file path does not exist on the file system: /var/folders/.../swift-generated-sources/@__swiftmacro_18MacroFeedbackRepro20MountActivationState17PreservedRawValuefMm_.swift That makes me suspect this is not an application logic issue, but something in macro expansion / generated source handling / compiler pipeline.
2
0
1.2k
1w
spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)
I'm distributing a macOS .pkg installer signed with Developer ID Installer and notarized via notarytool. On macOS 26.3 (Tahoe, Build 25D125), the package is rejected by Gatekeeper when downloaded from the internet. What works: pkgutil --check-signature → signed, Developer ID Installer, full chain (G2 intermediate + Apple Root CA) xcrun stapler validate → The validate action worked! xcrun notarytool info → status: Accepted The .app inside the .pkg passes spctl -a -vvv → accepted, source=Notarized Developer ID What fails: spctl -a -vvv --type install mypackage.pkg → rejected, origin=Developer ID Installer Raw assessment: assessment:remote = true, assessment:verdict = false Double-clicking the downloaded .pkg shows only Move to Trash / Done (no Open option) syspolicyd log: meetsDeveloperIDLegacyAllowedPolicy = 0 (expected, since the cert is new), but no notarized match is logged Certificate details: Developer ID Installer, issued Feb 28, 2026, valid until 2031 OID 1.2.840.113635.100.6.1.14 (Developer I
5
0
788
1w
Reply to spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)
[quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] Here's the direct download link to the installer package: [/quote] That link doesn’t work for me (I get a 404). This: [quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] The productbuild --sign does emit Warning: unable to build chain to self-signed root [/quote] is very concerning. It suggests that the signature was created without the full certificate chain, which could easily cause problems like this. When signing code, rather than an installer package, this is actually a hard failure. I talk about it in detail in Resolving errSecInternalComponent errors during code signing and the associated Fixing an untrusted code signing certificate. So: You should definitely do what you can to investigate and resolve the unable to build chain to self-signed root warning. If that doesn’t pan out, reply back here with a download link that works and I’ll take a look. Share and
Topic: Code Signing SubTopic: Notarization Tags:
1w
Face ID (LAContext) authenticate() causes SIGABRT crash immediately on iOS (Flutter local_auth)
I am developing a Flutter iOS application and encountering a crash when using biometric authentication (Face ID) via the local_auth plugin. ■ Environment Flutter: 3.x local_auth: 2.2.0 (also tested with 2.1.6) iOS: real device (Face ID is working normally for device unlock) Firebase Authentication (email/password) Xcode build ■ Issue When calling biometric authentication, the app crashes immediately. Code: final didAuthenticate = await auth.authenticate( localizedReason: 'Authenticate to login', options: const AuthenticationOptions( biometricOnly: false, useErrorDialogs: false, ), ); ■ Error Thread 1: signal SIGABRT Crash occurs in libsystem_kernel.dylib (__pthread_kill) Happens immediately when authenticate() is called No exception is caught in Dart (native crash) ■ Verified NSFaceIDUsageDescription is correctly included in Info.plist Confirmed it exists in the built Runner.app Info.plist localizedReason is non-empty and in English Flutter clean / pod install executed App reinstalled on device Face
1
0
223
1w
Reply to Attached macro loses generated source file
[quote='819975021, tiandt, /thread/819975, /profile/tiandt'] I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. [/quote] Agreed. I recommend that you file a bug about this. Please post your bug number, just for the record. If you use Xcode to expand the macro, what does it show? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Programming Languages SubTopic: Swift Tags:
1w
FIFinderSync Extension fails to load on FIFinderSync Extension fails to load on macOS 26.3.1 (a) (25D771280a)
(! status in pluginkit, FinderSyncExtensionHost process missing) macOS Version: 26.3.1 Beta (25D771280a) Xcode Version: 16.3 (17C529) Steps to reproduce: Create a Finder Sync Extension project Build and install to /Applications Enable in System Settings → Extensions → Finder Extensions Extension shows ! in pluginkit output FinderSyncExtensionHost process never starts Context menu never appears in Finder Expected: Extension loads and context menu appears Actual: Extension marked with ! in pluginkit, no process launched pluginkit output: ! com.github.astronautJack.EasyNewFile.EasyNewFileExtension(1.0)
1
0
51
1w
Reply to FIFinderSync Extension fails to load on FIFinderSync Extension fails to load on macOS 26.3.1 (a) (25D771280a)
If you set up a VM that’s never seen your app before and repeat this test on that VM [1], does it have the same problem. I’ve hunted app extension problems like this in the past, and it was always caused by weird issue on my main work Mac. Specifically, old school app extensions [2] rely PluginKit which relies on Launch Services, and it’s very common for Launch Services to behave weirdly on your main development Mac. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] You don’t need to build on the VM. Rather, build on your main Mac and then copy the built app to the VM. [2] Modern app extension are based on ExtensionKit rather than PluginKit, but they also rely on Launch Services.
1w
Reply to App review process takes long time
Hello iOS Developer Community, I have two apps stuck in Waiting for Review and would appreciate any advice from developers who have faced a similar situation. 📱 App 1 — BookAstors (User App) Submission ID: 33bc446c-42aa-425d-9eba-2b79e88e9c9f Version: iOS 1.0.4 (Build 15) Date Submitted: March 17, 2026 Waiting since: 6+ days 📱 App 2 — Admin BookAstors (Admin Panel) Submission ID: c8af128f-0666-492a-bd88-3a2cad64d74c Version: iOS 1.0.5 (Build 8) Date Submitted: February 28, 2026 Waiting since: 23+ days Both apps are live on the App Store with an active user base. These updates contain critical bug fixes that our users and business operators are waiting on. The delay is directly impacting user experience and platform operations. I submitted an Expedited Review Request for both apps and received Apple's confirmation: We'll expedite review for BookAstors / Admin BookAstors. However, even after the expedited request was accepted, neither app has moved from Waiting for Review to In Review. Has a
1w
After launching my first iOS app as an indie developer, what actions matter most now? 🚀📱
Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬
1
0
61
1w
What steps should I follow to get started with iOS development?
Hey everyone 👋 I’m starting my journey in iOS app development coming from a Java background and I already have an app idea but want to approach things the right way so I’d love your guidance What AI tools do you recommend for coding debugging and learning Swift or SwiftUI 🤖 how do you approach app design 🎨 and where do you find UI inspiration graphics or useful resources for building apps 🚀 any tips or lessons learned would really help 🙏
1
0
40
1w
Massive CoreML latency spike on live AVFoundation camera feed vs. offline inference (CPU+ANE)
Hello, I’m experiencing a severe performance degradation when running CoreML models on a live AVFoundation video feed compared to offline or synthetic inference. This happens across multiple models I've converted (including SCI, RTMPose, and RTMW) and affects multiple devices. The Environment OS: macOS 26.3, iOS 26.3, iPadOS 26.3 Hardware: Mac14,6 (M2 Max), iPad Pro 11 M1, iPhone 13 mini Compute Units: cpuAndNeuralEngine The Numbers When testing my SCI_output_image_int8.mlpackage model, the inference timings are drastically different: Synthetic/Offline Inference: ~1.34 ms Live Camera Inference: ~15.96 ms Preprocessing is completely ruled out as the bottleneck. My profiling shows total preprocessing (nearest-neighbor resize + feature provider creation) takes only ~0.4 ms in camera mode. Furthermore, no frames are being dropped. What I've Tried I am building a latency-critical app and have implemented almost every recommended optimization to try and fix this, but the camera-feed penalty remains: Matche
5
0
714
1w
Incorrect keyboard frame on iOS 26 when using Secure Text with Autofill
Area: Software Update Type of Feedback: Application Bug Description Device: iPhone 13 Pro running iOS 26 Build environment: Xcode 16.4 Problem description: When a text field has secureTextEntry = YES and Password Autofill / Passkeys is active, the autofill panel is not included in the rect reported from the keyboard notifications (UIKeyboardFrameEndUserInfoKey or others). As a result, when calculating the offset to move the screen up and reveal the hidden input field, the field is not displayed correctly because the reported keyboard height is smaller than the actual visible height. Observed behavior: This only occurs on devices running iOS 26 built with Xcode 16.4. On previous versions of iOS, with the same settings (secureTextEntry and Autofill active), the rect correctly includes the autofill panel height, and the UI works as expected. I tested with both UIKeyboardDidShowNotification and UIKeyboardWillChangeFrameNotification, and in both cases the behavior is the same: the height is incorrect (sma
3
0
754
1w
TestFlight build visible on macOS but not installable: “Can only be tested on an iOS device” for Mac (Designed for iPad)
Hello everyone. We have an app that has been on the App Store for several years, originally distributed for iOS and iPadOS only. Recently, we enabled Mac (Designed for iPad) and started distributing macOS-compatible builds. Current situation: The app is available and downloadable from the macOS App Store and runs correctly on Apple Silicon Macs. The same app/build appears in TestFlight on macOS, but cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatible, but TestFlight is treating the build as iOS-only. Environment and checks performed: Mac is Apple Silicon. App Store Connect app-level availability for Mac (Designed for iPad) is enabled. The app is not Mac Catalyst; it is a UIKit iOS/iPadOS app. Distribution is done via GitLab CI. CI uploads use an App Store provisioning profile (Apple Distribution), not development or ad-hoc. iPhone and iPad TestFlight installs work as expected. Info.plist ve
Replies
1
Boosts
0
Views
166
Activity
1w
Xcode 26 Warning: (arm64) empty dSYM file detected despite correct build settings
Hi Guys, Hope you're well! I am consistently encountering a build warning in Xcode 26 that prevents proper symbolication of crash logs. The warning states: warning: (arm64) /Users/mickey/Library/Developer/Xcode/DerivedData/CalendarSync-bjuvwxojzofqzzcmzzpdozbujrge/Build/Products/Debug-iphoneos/CalendarSync.app/CalendarSync empty dSYM file detected, dSYM was created with an executable with no debug info. Steps to Reproduce: Open the project in Xcode 26. Build the project for a physical iOS device (arm64) or Archive the project. The warning appears during the Generate dSYM phase of the build process. Troubleshooting Steps Already Taken (Issue Persists): Set 'Enable Debug Dylib Support' to No. Verified 'Debug Information Format' is set to 'DWARF with dSYM File'. Verified 'Generate Debug Symbols' is set to Yes. Set 'Strip Debug Symbols During Copy' and 'Strip Linked Product' to No. Performed 'Clean Build Folder' and manually deleted the DerivedData folder. The issue pe
Replies
2
Boosts
0
Views
74
Activity
1w
Attached macro loses generated source file
I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. Environment: Xcode 26.4 RC (17E192, latest); I believe it is also reproducible on earlier versions. github source code I reduced this to a very small macOS/iOS app plus a local macro package. The app logic is trivial, but app exits immediately on launch with code 138 Important observations: If I inline everything into a single file, the problem disappears. I also see an error like this during investigation: The file path does not exist on the file system: /var/folders/.../swift-generated-sources/@__swiftmacro_18MacroFeedbackRepro20MountActivationState17PreservedRawValuefMm_.swift That makes me suspect this is not an application logic issue, but something in macro expansion / generated source handling / compiler pipeline.
Replies
2
Boosts
0
Views
1.2k
Activity
1w
spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)
I'm distributing a macOS .pkg installer signed with Developer ID Installer and notarized via notarytool. On macOS 26.3 (Tahoe, Build 25D125), the package is rejected by Gatekeeper when downloaded from the internet. What works: pkgutil --check-signature → signed, Developer ID Installer, full chain (G2 intermediate + Apple Root CA) xcrun stapler validate → The validate action worked! xcrun notarytool info → status: Accepted The .app inside the .pkg passes spctl -a -vvv → accepted, source=Notarized Developer ID What fails: spctl -a -vvv --type install mypackage.pkg → rejected, origin=Developer ID Installer Raw assessment: assessment:remote = true, assessment:verdict = false Double-clicking the downloaded .pkg shows only Move to Trash / Done (no Open option) syspolicyd log: meetsDeveloperIDLegacyAllowedPolicy = 0 (expected, since the cert is new), but no notarized match is logged Certificate details: Developer ID Installer, issued Feb 28, 2026, valid until 2031 OID 1.2.840.113635.100.6.1.14 (Developer I
Replies
5
Boosts
0
Views
788
Activity
1w
Reply to spctl --type install rejects notarized .pkg on macOS 26 Tahoe (26.3)
[quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] Here's the direct download link to the installer package: [/quote] That link doesn’t work for me (I get a 404). This: [quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] The productbuild --sign does emit Warning: unable to build chain to self-signed root [/quote] is very concerning. It suggests that the signature was created without the full certificate chain, which could easily cause problems like this. When signing code, rather than an installer package, this is actually a hard failure. I talk about it in detail in Resolving errSecInternalComponent errors during code signing and the associated Fixing an untrusted code signing certificate. So: You should definitely do what you can to investigate and resolve the unable to build chain to self-signed root warning. If that doesn’t pan out, reply back here with a download link that works and I’ll take a look. Share and
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
1w
Face ID (LAContext) authenticate() causes SIGABRT crash immediately on iOS (Flutter local_auth)
I am developing a Flutter iOS application and encountering a crash when using biometric authentication (Face ID) via the local_auth plugin. ■ Environment Flutter: 3.x local_auth: 2.2.0 (also tested with 2.1.6) iOS: real device (Face ID is working normally for device unlock) Firebase Authentication (email/password) Xcode build ■ Issue When calling biometric authentication, the app crashes immediately. Code: final didAuthenticate = await auth.authenticate( localizedReason: 'Authenticate to login', options: const AuthenticationOptions( biometricOnly: false, useErrorDialogs: false, ), ); ■ Error Thread 1: signal SIGABRT Crash occurs in libsystem_kernel.dylib (__pthread_kill) Happens immediately when authenticate() is called No exception is caught in Dart (native crash) ■ Verified NSFaceIDUsageDescription is correctly included in Info.plist Confirmed it exists in the built Runner.app Info.plist localizedReason is non-empty and in English Flutter clean / pod install executed App reinstalled on device Face
Replies
1
Boosts
0
Views
223
Activity
1w
Reply to Attached macro loses generated source file
[quote='819975021, tiandt, /thread/819975, /profile/tiandt'] I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. [/quote] Agreed. I recommend that you file a bug about this. Please post your bug number, just for the record. If you use Xcode to expand the macro, what does it show? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
1w
FIFinderSync Extension fails to load on FIFinderSync Extension fails to load on macOS 26.3.1 (a) (25D771280a)
(! status in pluginkit, FinderSyncExtensionHost process missing) macOS Version: 26.3.1 Beta (25D771280a) Xcode Version: 16.3 (17C529) Steps to reproduce: Create a Finder Sync Extension project Build and install to /Applications Enable in System Settings → Extensions → Finder Extensions Extension shows ! in pluginkit output FinderSyncExtensionHost process never starts Context menu never appears in Finder Expected: Extension loads and context menu appears Actual: Extension marked with ! in pluginkit, no process launched pluginkit output: ! com.github.astronautJack.EasyNewFile.EasyNewFileExtension(1.0)
Replies
1
Boosts
0
Views
51
Activity
1w
Reply to FIFinderSync Extension fails to load on FIFinderSync Extension fails to load on macOS 26.3.1 (a) (25D771280a)
If you set up a VM that’s never seen your app before and repeat this test on that VM [1], does it have the same problem. I’ve hunted app extension problems like this in the past, and it was always caused by weird issue on my main work Mac. Specifically, old school app extensions [2] rely PluginKit which relies on Launch Services, and it’s very common for Launch Services to behave weirdly on your main development Mac. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] You don’t need to build on the VM. Rather, build on your main Mac and then copy the built app to the VM. [2] Modern app extension are based on ExtensionKit rather than PluginKit, but they also rely on Launch Services.
Replies
Boosts
Views
Activity
1w
Reply to App review process takes long time
Hello iOS Developer Community, I have two apps stuck in Waiting for Review and would appreciate any advice from developers who have faced a similar situation. 📱 App 1 — BookAstors (User App) Submission ID: 33bc446c-42aa-425d-9eba-2b79e88e9c9f Version: iOS 1.0.4 (Build 15) Date Submitted: March 17, 2026 Waiting since: 6+ days 📱 App 2 — Admin BookAstors (Admin Panel) Submission ID: c8af128f-0666-492a-bd88-3a2cad64d74c Version: iOS 1.0.5 (Build 8) Date Submitted: February 28, 2026 Waiting since: 23+ days Both apps are live on the App Store with an active user base. These updates contain critical bug fixes that our users and business operators are waiting on. The delay is directly impacting user experience and platform operations. I submitted an Expedited Review Request for both apps and received Apple's confirmation: We'll expedite review for BookAstors / Admin BookAstors. However, even after the expedited request was accepted, neither app has moved from Waiting for Review to In Review. Has a
Replies
Boosts
Views
Activity
1w
After launching my first iOS app as an indie developer, what actions matter most now? 🚀📱
Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬
Replies
1
Boosts
0
Views
61
Activity
1w
Reply to What steps should I follow to get started with iOS development?
Start with Swift basics then learn Xcode build small apps follow tutorials and practice consistently 🌟📲
Replies
Boosts
Views
Activity
1w
What steps should I follow to get started with iOS development?
Hey everyone 👋 I’m starting my journey in iOS app development coming from a Java background and I already have an app idea but want to approach things the right way so I’d love your guidance What AI tools do you recommend for coding debugging and learning Swift or SwiftUI 🤖 how do you approach app design 🎨 and where do you find UI inspiration graphics or useful resources for building apps 🚀 any tips or lessons learned would really help 🙏
Replies
1
Boosts
0
Views
40
Activity
1w
Massive CoreML latency spike on live AVFoundation camera feed vs. offline inference (CPU+ANE)
Hello, I’m experiencing a severe performance degradation when running CoreML models on a live AVFoundation video feed compared to offline or synthetic inference. This happens across multiple models I've converted (including SCI, RTMPose, and RTMW) and affects multiple devices. The Environment OS: macOS 26.3, iOS 26.3, iPadOS 26.3 Hardware: Mac14,6 (M2 Max), iPad Pro 11 M1, iPhone 13 mini Compute Units: cpuAndNeuralEngine The Numbers When testing my SCI_output_image_int8.mlpackage model, the inference timings are drastically different: Synthetic/Offline Inference: ~1.34 ms Live Camera Inference: ~15.96 ms Preprocessing is completely ruled out as the bottleneck. My profiling shows total preprocessing (nearest-neighbor resize + feature provider creation) takes only ~0.4 ms in camera mode. Furthermore, no frames are being dropped. What I've Tried I am building a latency-critical app and have implemented almost every recommended optimization to try and fix this, but the camera-feed penalty remains: Matche
Replies
5
Boosts
0
Views
714
Activity
1w
Incorrect keyboard frame on iOS 26 when using Secure Text with Autofill
Area: Software Update Type of Feedback: Application Bug Description Device: iPhone 13 Pro running iOS 26 Build environment: Xcode 16.4 Problem description: When a text field has secureTextEntry = YES and Password Autofill / Passkeys is active, the autofill panel is not included in the rect reported from the keyboard notifications (UIKeyboardFrameEndUserInfoKey or others). As a result, when calculating the offset to move the screen up and reveal the hidden input field, the field is not displayed correctly because the reported keyboard height is smaller than the actual visible height. Observed behavior: This only occurs on devices running iOS 26 built with Xcode 16.4. On previous versions of iOS, with the same settings (secureTextEntry and Autofill active), the rect correctly includes the autofill panel height, and the UI works as expected. I tested with both UIKeyboardDidShowNotification and UIKeyboardWillChangeFrameNotification, and in both cases the behavior is the same: the height is incorrect (sma
Replies
3
Boosts
0
Views
754
Activity
1w