개발자 노트

The Problem I was facing an issue where the spacing between the question, image, and options was excessively large, resulting in poor readability. On top of that, constraint conflicts were occurring. The root cause was that it is mathematically impossible for Auto Layout to satisfy the following three constraints simultaneously: 20pt spacing from the question to the image view. 10pt spacing from the question label to the options stack view. 20pt spacing from the image view to the options stack view. The Solution To resolve this, I made the constraints dynamic. First, declare variables for the constraints: Swift private var questionToOptionsConstraint: NSLayoutConstraint ! private var questionToImageConstraint: NSLayoutConstraint ! private var imageToOptionsConstraint: NSLayoutConstraint ! Next, initialize these constraints in the setupConstraints() method, but do not activate them yet: Swift questionToOptionsConstraint = optionsStackView.topAnchor.constraint(equalTo: questio...

1. Preventing Data Conflicts with a Composite Primary Key Problem Previously, the level and quizGroup were not distinctly separated in the database. As a result, saving new progress would unintentionally overwrite existing data from other levels. Solution I updated the progress table to use a composite primary key consisting of both level and quizGroup . This ensures that progress is managed independently for each specific level and group. SQL CREATE TABLE IF NOT EXISTS progress ( level TEXT, quizGroup TEXT, lastQuestionIndex INTEGER , PRIMARY KEY (level, quizGroup) ); 2. Improving the Data Saving Mechanism Updating Progress for a Specific Level and Group In the saveProgress method, I updated the SQL query to include both level and quizGroup in the WHERE clause. This ensures we only update the progress for the targeted level and group. Swift let updateQuery = "UPDATE progress SET lastQuestionIndex = ? WHERE level = ? AND quizGroup = ?;" Appl...

 This guide explains how to configure your Git repository to ignore the Info.plist file when pushing an Xcode project to GitHub. 1. Update Your .gitignore File First, you need to configure Git to ignore the Info.plist file. ① Check for a .gitignore file Bash ls -a If the file doesn't exist, create one: Bash touch .gitignore ② Edit the .gitignore file Open the file and add the following line: Plaintext # Ignore Xcode Info.plist file **/Info.plist 2. Remove an Already Tracked Info.plist from Git If the file has already been committed and pushed to GitHub, you need to manually remove it from Git's tracking index. ① Untrack Info.plist Bash git rm --cached path/to/Info.plist Example: Bash git rm --cached MyApp/Info.plist ② Commit and push the changes Bash git commit -m "Ignore Info.plist" git push origin main 3. Managing Info.plist for Team Collaboration Since Info.plist is now ignored, other developers won't have it when they clone the repository. To solve t...

1. Check if Info.plist is Currently Tracked by Git First, open your terminal, navigate to your project directory, and run the following command: Bash git ls-files | grep Info.plist If the file path to your Info.plist is displayed in the output, it means Git is currently tracking the file. Example Output: Plaintext ios/ExampleApp/Info.plist Now, let's remove this file from Git tracking and ensure it gets ignored moving forward. 2. Add Info.plist to Your .gitignore File Modify your .gitignore file to prevent Git from staging the Info.plist file in the future. How to update .gitignore : Check if a .gitignore file exists in your project's root directory. If it doesn't exist, create one by running touch .gitignore in the terminal. Open the .gitignore file and add the following lines: Plaintext # Ignore Info.plist ios/ExampleApp/Info.plist ⚠ Important: Make sure to replace ios/ExampleApp/Info.plist with the actual file path of the Info.plist in your project. 3. Remove...