Electron-Forge Publishing Native MacOS App to App Store | Debug Errors on pkg | App Already functions

I am looking for a freelancer who can assist me in publishing a Native MacOS app to the App Store using Electron-Forge. The app is already functioning properly but needs to be packaged for the App Store. Programming Language: JavaScript, Electron, Electron Forge Specific requirements and guidelines for the packaging process have been provided and must be followed. Ideal Skills and Experience: - Experience with Electron-Forge and packaging apps for the App Store - Proficiency in JavaScript programming language - Knowledge of MacOS app development and publishing process Gig Details as follows: I am the developer of a Wallpaper setting app that requires assistance in distributing an app natively on the Mac App Store. The app, built using electron-forge and signed with electron-osx-sign, encounters errors during submission via the Transporter app. The primary focus is on resolving issues related to Apple Certificates and Electron build, with the distribution process expected to be similar to that for an iOS app. The app is currently fully functional locally when running `npm start`. Expecting to be 3-7 hours of work. Upon interest, given you have expertise and knowledge in Electron with Mac and publishing to Mac App Store, I can provide you the project's files and error list. Tasks: • Review all the Errors from Transporter (see below) to understand the current issues. ◦ Familiarize with the project structure: ◦ Root directory: 'wallpapers' ◦ Electron project in wallpapers/electron-forge-project • Run npm install in the root directory and wallpapers/electron-forge-project directory. • Test the app locally using npm start to check for functionality and replicate errors. Examine the [login to view URL] files for potential issues with package dependencies. As of right now, on Click of a button while the electron app is running, the user's Mac Desktop Background is set. • Package the app to be ready for Transporter, with the icon provided as an attachment to this post • Upload to your own Apple Developer account. If it works, it will likely also work for my own Apple Developer account later (with a different bundle ID). Transporter shows the following I have provided most of the errors I could fit at the bottom, there are currently 10 errors in total, which you can have given you have knowledge and expertise: Asset validation failed (90285) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, key '[login to view URL]' in '[login to view URL] [login to view URL] Helper' is not supported. (ID: d92e7486-4966-4744-830e-8fb9db995ad4) Asset validation failed (90285) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, key '[login to view URL]' in '[login to view URL]' is not supported. (ID: 6453dcf6-73bf-489b-a530-9b9e9dab76db) Asset validation failed (90285) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, key '[login to view URL]' in '[login to view URL] [login to view URL] Framework' is not supported. (ID: 3a35268f-bb2f-4fd5-864a-468e0ce0a23f) Asset validation failed (90285) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, key '[login to view URL]' in '[login to view URL]' is not supported. (ID: fb4c9252-f5d0-44f7-aaf0-69084efecc54) Asset validation failed (90255) The installer package includes files that are only readable by the root user. This will prevent verification of the application's code signature when your app is run. Ensure that non-root users can read the files in your app. (ID: 3ae9eee2-fcda-4e45-b46c-ec625510ad91) Asset validation failed (90236) Missing required icon. The application bundle does not contain an icon in ICNS format, containing both a 512x512 and a 512x512@2x image. For further assistance, see the Human Interface Guidelines at [login to view URL] (ID: eb6c8efb-2d2a-4d07-83e5-bbeab2b5db9e) Asset validation failed (90869) Invalid bundle. The “[login to view URL]” bundle supports arm64 but not Intel-based Mac computers. Your build must include the x86_64 architecture to support Intel-based Mac computers. To support arm64 only, your macOS deployment target must be 12.0 or higher. For details, view: [login to view URL] (ID: d4c12cb2-ad87-4891-b2fc-0a93adad194c) Asset validation failed (90285) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, key '[login to view URL]' in '[login to view URL]' is not supported. (ID: 904a9a19-a398-4227-89d4-3deec2144cef) If interested, in your proposal please respond with answers to these two questions. In 1-3 sentences, what is your expertise with Electron publishing to the Mac App Store? Have you ever done it? It is not necessarily bad if not, but would like to hear how you might be able to help if you don't have experience with it specifically. In 1-3 sentences, what is your expertise with Apple Certificates?