Patch 5 (#50)

neoarz · web-flow · commit 9431bc353c38 · 2024-12-20T21:19:56.000-05:00
* Update sparserestore.mdx

Signed-off-by: neoarz &lt;164915254+neoarz@users.noreply.github.com&gt;

* Update faq.mdx

Signed-off-by: neoarz &lt;164915254+neoarz@users.noreply.github.com&gt;

* Update faq.mdx

Signed-off-by: neoarz &lt;164915254+neoarz@users.noreply.github.com&gt;

* Update prerequisites.mdx

Signed-off-by: neoarz &lt;164915254+neoarz@users.noreply.github.com&gt;

* Update pairing-file.mdx

Signed-off-by: neoarz &lt;164915254+neoarz@users.noreply.github.com&gt;

* Update pairing-file.mdx

Signed-off-by: neoarz &lt;164915254+neoarz@users.noreply.github.com&gt;

---------

Signed-off-by: neoarz &lt;164915254+neoarz@users.noreply.github.com&gt;
diff --git a/docs/faq.mdx b/docs/faq.mdx
@@ -54,7 +54,7 @@ Normally, no, as that’s an iOS and developer account limitation. Apple only al
 
 To remove this restriction (and also get a 365 day expiry), you can pay for a $99/year Apple Developer account.
 
-Alternatively, there is currently a nightly build available [here](https://github.com/SideStore/SideStore/releases/tag/nightly) (version 0.5.9-nightly.2024.10.23.1+1e969a0 as of writing) that utilises the SparseRestore exploit to bypass the 3-app limit. Currently, this only works on iOS versions below 18 dev beta 5 plus 18.0.1 for definite.
+Alternatively, there is currently a nightly build available [here](https://github.com/SideStore/SideStore/releases/tag/nightly) (version 0.5.9-nightly.2024.10.23.1+1e969a0 as of writing) that utilizes the SparseRestore exploit to bypass the 3-app limit. Currently, this only works on iOS versions below 18 dev beta 5 plus 18.0.1 for definite.
 
 A tutorial for using this can be found [here](advanced/sparserestore).
 
@@ -72,7 +72,7 @@ Nope, as currently it acts like AltStore while signing.
 
 ### As a user, I’m having trouble logging into SideStore. I get an error
 
-There is many reasons this can happen, but the most common issue is a temporary Anisette server downtime. You can currently change the Anisette server on your device’s Settings app in SideStore under “Anisette URL”.
+There are many reasons this can happen, but the most common issue is a temporary Anisette server downtime. You can currently change the Anisette server on your device’s Settings app in SideStore under “Anisette URL”.
 
 ### Is SideStore going to have a Storefront?
 
@@ -126,7 +126,7 @@ Don't panic! Re-sideload the apps without removing them from your device, and yo
 
 ### I'm unable to select my pairing file with any file type
 
-Make sure your pairing file's extension ends with `.mobiledevicepairing` or `.plist`. If it doesn't, double check to see if you had zipped your pairing file before sending it to your phone. Failing to do so may lead to the file breaking during transport. Also, when signing Sidestore with a certificate, you won't be able to select the pairing file from within app. You can try moving the pairing file to the root directory of the SideStore folder in the Files app in "On My iPhone/iPad", and naming it `ALTPairingFile.mobiledevicepairing`. If you do not see the Sidestore folder in the files app, connect your phone to your computer, and you can drag and drop the pairing file to the files of the Sidestore app. Ensure to change it to name mentioned above. Note that it is case sensitive.
+Make sure your pairing file's extension ends with `.mobiledevicepairing` or `.plist`. If it doesn't, double check to see if you had zipped your pairing file before sending it to your phone. Failing to do so may lead to the file being corrupted during transport. Also, when signing Sidestore with a certificate, you won't be able to select the pairing file from within app. You can try moving the pairing file to the root directory of the SideStore folder in the Files app in "On My iPhone/iPad", and naming it `ALTPairingFile.mobiledevicepairing`. If you do not see the Sidestore folder in the files app, connect your phone to your computer, and you can drag and drop the pairing file to the files of the Sidestore app. Ensure to change it to name mentioned above. Note that it is case sensitive.
 
 ### Cannot start DebugServer
 
@@ -138,6 +138,6 @@ To start the process of using a new pairing file you go to settings tab and clic
 
 ### Currently Known issues
 
-If your currently having issues and want to know if we already know about them. Then check out our GitHub issue that has list of known issues and ways to mitigate some of the issues you might be having. Some of the issues in this list might be known that are not there, but are in the GitHub issues section. https://github.com/SideStore/SideStore/issues/490
+If you're currently having issues and want to know if we already know about them. Then check out our GitHub issue page which  has a list of known issues and ways to mitigate some of the issues you might be having. Some of the issues in this list might be known that are not there, but are in the GitHub issues section. https://github.com/SideStore/SideStore/issues/490
 
 If you have any issues that aren't in this list. Just make a GitHub issue or [join our discord.](https://discord.gg/sidestore-949183273383395328)
diff --git a/docs/getting-started/pairing-file.mdx b/docs/getting-started/pairing-file.mdx
@@ -16,7 +16,7 @@ Download Jitterbugpair for [Windows (64-bit)](https://github.com/osy/Jitterbug/r
 2. Plug your device into your computer, and open your device to its home screen. Once done, execute the program.
     * Your device may ask you to trust your computer. Make sure to accept this prompt, as it is required for the pairing process.
 3. Once it is done, you will get a file that ends with `.mobiledevicepairing`.
-4. Transfer this file to your device using iTunes, or any other method.
+4. Transfer this file to your device using iTunes, or any other method. Zipping the file before sending it off is the best way to ensure the pairing file won't break during transport.
     * Transferring using cloud storage may change the file's extension (most likely turning into a .txt file), so be careful. It is also possible to change the extension to `.plist` for use with older SideStore versions, like `0.1.1`.
 
 On Windows, you might have to execute the program using Command Prompt or Powershell, as it can sometimes not open by double clicking the `.exe` file.
@@ -34,7 +34,8 @@ On Windows, you might have to execute the program using Command Prompt or Powers
 3. Open Terminal. (In launchpad its in the "Utilities" folder)
 4. Drag the jitterbugpair file into Terminal and press "Return" or Enter. (Make sure your device is plugged in)
     * If you get "macOS cannot verify that this app is free from malware" put into terminal `xattr -c ` (with a space after) then drag jitterbugpair then press enter. after that try doing step number 4 again.
-5. Transfer this file to your device in a way of your choosing.
+5. If you are unable to find the pairing file after running jitterbugpair, try copying the name of the pairing file generated, and pasting it into Finder. If you created multiple pairing files all of them should show up since pairing files all have the name for the device they are tied to.
+6. Transfer this file to your device in a way of your choosing. Zipping the file before sending it off is the best way to ensure the pairing file won't break during transport.
     * Transferring using cloud storage may change the file's extension (most likely turning into a .txt file), so be careful. It is also possible to change the extension to `.plist` for use with older SideStore versions, like `0.1.1`.
 
 ### Linux
@@ -46,7 +47,7 @@ These instructions expect that you are familiar with the linux commandline.
 3. Plug your device into your computer, and open your device to its home screen. Once done, execute the program in your terminal with `./jitterbugpair`
     * If you get a prompt saying you need to trust the computer from your iDevice, make sure to do so. You may need to rerun jitterbugpair.
 4. Once it is done, you will get a file that ends with `.mobiledevicepairing` in the directory you ran jitterbugpair from.
-5. Transfer this file to your device in a way of your choosing.
+5. Transfer this file to your device in a way of your choosing. Zipping the file before sending it off is the best way to ensure the pairing file won't break during transport
     * Transferring using cloud storage may change the file's extension (most likely turning into a .txt file), so be careful. It is also possible to change the extension to `.plist` for use with older SideStore versions, like `0.1.1`.
 
 You might have success with just adding execute permissions and running jitterbugpair from a file manager, but it is recommended to just do it from the terminal.
diff --git a/docs/getting-started/prerequisites.mdx b/docs/getting-started/prerequisites.mdx
@@ -22,7 +22,7 @@ Users of iOS/iPadOS 16 or higher *must* have Developer Mode enabled. Do this by:
 
 ## WireGuard
 
-SideStore utilitizes an on-device WireGuard VPN which allows SideStore to communicate to internal services.
+SideStore utilizes an on-device WireGuard VPN which allows SideStore to communicate to internal services.
 
 1. Download the WireGuard app from the [Official App Store](https://apps.apple.com/us/app/wireguard/id1441195209).
 2. Also, download the WireGuard config found [here.](https://github.com/SideStore/SideStore/releases/download/0.3.1/SideStore.conf)
@@ -35,4 +35,4 @@ This VPN is required to be on any time you use SideStore, as most functions will
 
 ## Next Steps 
 
-Now, go to the next page to generate your pairing file!
+Now, go to the next page to generate your pairing file!
