Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
@yodaluca23
yodaluca23 authored Sep 5, 2024
1 parent ba6e073 commit 0d478ea
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ In version 2.1.0 the option to use Musixmatch as a lyric provider was added, you
</details>

## How it's Made<br/>
I post a new release every time there is an EeveeSpotify Update, or there is a new major Spotify update that is compatible with the latest EeveeSpotify. I get the vanilla Spotify IPA from IOS God's [Decrypted AppStore](https://armconverter.com/decryptedappstore/us/spotify), from green verified links on [AppDB](https://appdb.to/app/ios/324684580), or using [this fork of BagBak](https://github.com/TbhLovers/bagbak), with my personal jailbroken iPhone XR. I will specify details on each release page. Then I download the latest EeveeSpotify .deb and SwiftProtobuf framework .deb (dependency) from Eevee's release page [here](https://github.com/whoeevee/EeveeSpotify/releases/latest) and Orion Runtime (iOS 14 - 16) off of Chariz [here](https://chariz.com/get/orion-runtime14) (it's a dependency). I download the tweaks directly from the sources. I then inject the .deb's into the Spotify IPA using [my fork](https://github.com/yodaluca23/pyzule) of [Pyzule](https://github.com/asdfzxcvbn/pyzule), and change the IPA version and Bundle ID to the SpotveeC version and Bundle ID. (For the AltStore Version) I do not do anything else to the IPA (Unless otherwise specified in the release notes)... However please note that theoretically, IOSGod's decrypted app store could insert malware, same with pyzule, Whoeevee's tweak, Whoeevee's Extension, the Orion runtime tweak, or aesthyrica's tweak, or anything else in the chain and/or environment. However, these are considered trusted by the community and/or open source. This is use at your own risk, and I am not responsible for *ANY* damage. All of this and more is automated using the completely open-source GitHub Workflow script available [here](https://github.com/SpotCompiled/SpotveeC/blob/main/.github/workflows/Build%20and%20Release.yml).
I post a new release every time there is an EeveeSpotify Update, or there is a new major Spotify update that is compatible with the latest EeveeSpotify. I get the vanilla Spotify IPA from IOS God's [Decrypted AppStore](https://armconverter.com/decryptedappstore/us/spotify), from green verified links on [AppDB](https://appdb.to/app/ios/324684580), or using [this fork of BagBak](https://github.com/TbhLovers/bagbak), with my personal jailbroken iPhone XR. I will specify details on each release page. Then I download the latest EeveeSpotify .deb and SwiftProtobuf framework .deb (dependency) from Eevee's release page [here](https://github.com/whoeevee/EeveeSpotify/releases/latest) and Orion Runtime (iOS 14 - 16) off of Chariz [here](https://chariz.com/get/orion-runtime14) (it's a dependency). I download the tweaks directly from the sources. I then inject the .deb's into the Spotify IPA using [my fork](https://github.com/yodaluca23/pyzule) of [Pyzule](https://github.com/asdfzxcvbn/pyzule), and change the IPA version and Bundle ID to the SpotveeC version and Bundle ID. (For the AltStore Version) I do not do anything else to the IPA (Unless otherwise specified in the release notes)... All of this and more is automated using the completely open-source GitHub Workflow script available [here](https://github.com/SpotCompiled/SpotveeC/blob/main/.github/workflows/Build%20and%20Release.yml).

Version Format is *SpotveeC Version*\_*Spotify Version*<br/>
Ex. *v1.3.6*\_*v8.7.78*<br/>
Expand All @@ -65,4 +65,10 @@ Ex. *v1.3.6*\_*v8.7.78*<br/>
[Am1nCmd- Spotify++](https://appdb.to/app/cydia/1900000540) *For ScreenShots*<br/>
[@RobyRew](https://github.com/RobyRew) *For helping me setup a lot of things*
***
<sup>We are not affiliated, associated, authorized, endorsed by, or in any way officially connected with any other company, agency, or government agency. All product and company names are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.</sup>
<sup>We are not affiliated, associated, authorized, endorsed by, or in any way officially connected with any other company, agency, or government agency. All product and company names are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

<sup>The software is provided "as is," without any warranties, whether express or implied, including but not limited to warranties of merchantability or fitness for a particular purpose. The developers make no guarantees regarding the software’s performance, reliability, or accuracy. In no event shall the developers be held liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the software or its use. Use of this software is at your own risk.

<sup>Furthermore, the software may utilize or depend on third-party software, libraries, or services. The developers are not liable for any issues, errors, or damages resulting from the use of such third-party components. The providers of those components are likewise not responsible for any liabilities arising from their use in this software.

<sup>By using this software, you acknowledge and accept full responsibility for any risks associated with its use.

0 comments on commit 0d478ea

Please sign in to comment.