Describe the bug After cloning the repository, running: make bootstrap-client and then opening the workspace file and attempting to run the main isowords target produces the following error: The stickers icon set or app icon set named "AppIcon" did not have any applicable content.

To reproduce

• Clone the repository
• Run make bootstrap-client in terminal
• Open workspace
• Run isowords target
• Build fails

Expected behavior The app runs in the iOS simulator

Screenshots/video

Environment

• 2016 MacBook Pro 15":
• OS: macOS 11.4

Thanks to a tip from @krzysztofzablocki we found out that we can get rid of the workspace if we hold the Xcode project in a sub-directory instead of the root, which we already do.

--- Solved --- But feel free to comment...

In the spirit of issue #49 I'll ask this question here - but please let me know if you'd prefer I ask it elsewhere (Twitter, StackOverflow, forums.swift.org - where is best?)

I'm interested in using Previews to view some of the available screens. I’m running into an issue I’m sure you had to solve early on in your development:

“unexpected service error: build aborted due to an internal error: planning Failed(“multiple configured targets of \’CubeCore\’ are being created for iOS Simulator”)

I see multiple proposed solutions, from setting the DISABLE_DIAMOND_PROBLEM_DIAGNOSTIC build setting to YES in the app target to converting static libraries to dynamic. What worked best for you?

This reinstalls the Setting reducer in Home reducer. It was most likely left behind during the "protocol" conversion.

As Reduce and the other ifLet reducers are not effectively handling .settings actions, they all commute with Settings, so this reducer can be installed arbitrarily at the end of the reducer's chain with the other child reducers.

This should fix #170

I also took the liberty to modernize homogenous EmptyReducer().ifCaseLet… into Scope(state: /CasePath…, but I can revert if you prefer.

As described in the title, I think it will be a good feature if we add a time limit for each turn in multiplayer mode. For example, there can be an adjustable time limit of say 1 minute before the person's turn is forfeited.

I will add more design details because I would actually like to work on this, once I get a better understanding of the codebase (just discovered this amazing project today).

I'm new to git-lfs and the version bootstrap tried to use caused a segmentation fault. I removed it and reinstalled using brew. Then I was asked to issue 'git lfs install' when I issued 'git-lfs' with no args. That worked fine. At this point I am cd-ed into isowords, and issue 'make bootstrap-client':

⚠️ Checking for Git LFS... ✅ Git LFS is good to go! touch Sources/AppAudioLibrary/Resources/empty.mp3 touch Sources/AppClipAudioLibrary/Resources/empty.mp3 /dev/stdin:173: INSERT failed: UNIQUE constraint failed: words.word /dev/stdin:236: INSERT failed: UNIQUE constraint failed: words.word --- for a total of 1468 similar lines

are these normal error messages that can be safely ignored?

Hello folks!

In the wake of the Part 2 episode of the isowords tour (and after collecting all the pieces of my brain from the floor after it has been 🤯-ed), I've decided to poke around the snapshot tests and noticed the AppStore images could be improved.

Here's a diff with my changes:

• Device and screen corners are now continuous
• Device and screen corner radii are now concentric
• Added cellular bars
• Status bar views are now horizontally centred in their corresponding ear
• Status bar bottom edge is visually aligned to the notch

In detail:

I hope this is useful!

P.S. I'm still salty that I'm #11 in on of the screenshots and it shows only the top 10 results...

Hi everyone 👋🏻

I am absoluty not proud of this one, because I needed 50 minutes to figure out what actually happened since I'm on a new device and didn't think twice about my tools installed. A more explicit error message will maybe help other lost souls like me 😅

If the language or format used in the message needs correction, I'm happy about every kind of feedback. Since then .. happy easter 🥚

Hi. Love the project and the way it is structured. I have tried to move one of my own apps over to a similar sort of scheme by following the setup of your package file

I am seeing a few flaky CI runs, sometimes testing passes and sometimes it fails.

the failure seems to be related to the resolution of XCTestDynamicOverlay

error: Missing package product 'XCTestDynamicOverlay' 

when I see this locally I can get rid of the issue by clearing my derived data which then prompts Xcode to do its thing and pull the dependencies again.

I know it may be difficult to diagnose without having a copy of my project, but I figure it was worth an ask. Maybe you guys have seen something similar? I am using an almost identical copy of your ci workflow and a paired down set of package dependencies. Hopefully I am missing something small.

I've started the Daily Unlimited challenge and then ended it without doing anything. Now the game doesn't let me play the challenge again which is fine, but the button isn't faded out.

I tried asking via Twitter, but I think my privacy settings were messed up. I was using the test version of isowords until you released it on the store, and then bought that version. I notice a lot of people have normal user names, whereas mine is a randomly generated string. Can I change my user name? If not, it's not a big deal... Alas, I'm afraid my days in the top ten are forever gone!

Describe the bug It seems like many of the viewStore actions sent within views of the Settings module (e.g. SoundsSettingsView) do not actually do anything within the Settings reducer as I'd expect. Instead, I see in the debug console a message like this:

2022-12-09 17:31:27.590658-0600 isowords[11473:1931144] [ComposableArchitecture] A binding action sent from a view store 
at "SettingsFeature/SoundsSettingsView.swift:22" was not handled. …

  Action:
    Settings.Action.binding(.set(_, 0.6017382))

To fix this, invoke "BindingReducer()" from your feature reducer's "body".

This is very strange because BindingReducer() is indeed within the Settings reducer body.

To reproduce If I compile isowords in Xcode, run the app, click on the settings button, select the sound button and try and change the value of any of the sound sliders, the sliders actually do not change value.

Expected behavior I'd expect that the Settings reducer would actually stop at any of the breakpoints I set within it.

Screenshots/video https://user-images.githubusercontent.com/67525430/206812842-45fda284-78ec-4908-8177-1ab66a1a5015.mov

Environment

• Device: iPhone 14 Simulator
• OS: iOS 16.1
• Xcode: 14.1

Additional context What is strange is that if I run "SettingsPreview", I do not see this problem.

After trying to figure out how to handle saving UserSettings in my own app (https://github.com/pointfreeco/swift-composable-architecture/discussions/1384) and reading the discussion about mutable environment states, I thought I'd give it a try to replace FileClient with a new PersistenceClient, which will use UserDefaults in the backend for saving user data.

Describe the bug Audio is turned off in isowords settings. Battery in System Settings is showing significant percentage of battery drain and Audio as the load.

To reproduce Turn audio off, run isowords for a couple of games, go to battery (an hour later) and look at the description.

Expected behavior If Audio is turned off isowords should be spending zero cpu cycles playing audio. Quick look at the code makes it seem like there aren't any checks for sound off and it just plays the audio with zero volume. You'd hope iOS would be smart about that, but it seems it may not be.

Screenshots/video

Environment

• Device: iPhone 12 Pro
• OS: iOS 15.5
• isowords build 102 (fe7eb2c)

This PR changes the majority of the code that is checking for iPad UI idiom to code that checks for "effectively using iPad metrics", which I've defined as "iPad idiom and horizontal size class not compact". With this change in place, the app will select UI element sizes and layout values (e.g. padding) that are intended for iPhone when running on iPad in compact width.

This fix contains a shortcut that is probably fine for an app such as isowords, but is incorrect in the general case. Namely, the horizontal size class is tracked in the DeviceState struct, which captures the horizontal size class high up in the view hierarchy, whereas it is OK for intermediate views to manually override this value. Thus, the horizontalSizeClass value in the SwiftUI Environment on the view where you want to apply the metrics is the real "truth" and could diverge from what is in DeviceState. However, that makes the code a lot messier since it introduces another environment property into each of these views, plus each test about what metrics to apply becomes idiom == pad && horizontalSizeClass != compact.

This change affects metrics and layout in the broader app, it's possible I've introduced some visual regressions since I've not tested all the flows extensively.

I have noticed some visual glitching when doing some rotation and the app is in compact width. I'm not certain if this is a regression or some artifact of running in the simulator. I was not successful getting the code signing to be generic enough to run a local build of the app on my devices.

If this problem is present when running on device, I don't mind working on it a little further if you have hints about where I should look.

An alternative "fix" for this problem would be to enable "requires full screen" in info.plist, which would stop supporting the multitasking scenarios completely.

Describe the bug iPad multitasking is enabled in info.plist, but the app has various layout issues when running side by side in compact width.

This is true even with the cube worldScale fix from #126

To reproduce

• Launch the app on iPad and use multitasking to put the app into compact width.
• rotate the iPad etc etc

Expected behavior Nothing is clipped and screen width is used effectively. It would probably be most effective if the iPad app in compact width used layout metrics similar to the phone app since compact width sizes are fairly similar.

Screenshots/video

some representative examples.

Environment

• iPad, iOS 14.7.1

I'm working on a PR to use the iPhone layout values when running on iPad in compact width.