I cannot play music with my bot on Heroku today, its written in Discord.js.
But I can play music very well at yesterday, I don't know what happened.(No any info in console)
At first I thought it was an error in my code. I changed the code to the previous version and the error appeared again...
I am using Node js 15 (14 has this issue too, already tried to use Node js 14)
Discord js fork by Matte(I don't think it's Djs's problem)
Heroku free dyno
discord-ytdl-core 5.0.0 with ytdl-core 4.4.4(Lasted)
You probably haven't installed the FFMPEG Buildpack for Heroku. This allowed me to play music on my bot.
If your bot can play locally and not on Heroku, this may be the solution for you:
Below is the link that gives you information on what this buildpack does.
https://elements.heroku.com/buildpacks/jonathanong/heroku-buildpack-ffmpeg-latest
Related
I have an app that was running on an older version of heroku and it no longer works, so I updated to the new stack but now I’m having trouble redeploying. I’ve played around with a few commands in the CLI but none I’ve seen on here have worked for me. Do I have to redeploy for the changes to take effect or is there a workaround? Any help would be much appreciated.
I have an application on play store to whom the targetSdkVersion is update to 30 from 29, which is getting rejected again and again by Google Play after an update.
Previously, there was a permission of MANAGE_EXTERNAL_STORAGE in one of the SDK Manifest.
After removing MANAGE_EXTERNAL_STORAGE permission and storage permission (WRITE_EXTERNAL_STORAGE) completely from my app, uploading the app on store, app update gets rejected again.
This is the email received from Google Play for the rejection reason.
Note: I am saving all my media files in app-specific internal storage.
Also, I have the permission of READ_EXTERNAL_STORAGE in my SDK as we have chat feature in our app to get images and videos of device to sent it.
According to Use of All files access (MANAGE_EXTERNAL_STORAGE) permission READ_EXTERNAL_STORAGE permission has not impact.
Attached reference.
Update
I also removed READ_EXTERNAL_STORAGE permission from the app, but still got the rejection with same reason from Google Play.
Is the issue with Storage Policy, or something else?
I had the same error for a month but finally, Google Play Store accepted my uploads.
Briefly, what I did was to create new builds for each track, and -interestingly- it worked!
(Before my countless update trials, our latest version on Production was 2.23.5 (build 1), our active tracks were Internal Testing Track and Production, and I was trying to upload my updates to Internal Testing Track.)
Below are the steps that I've applied:
Created a new build 2.24.1 (build 1) with all necessary changes. (e.g. upgrading targetSdkVersion to 30, removing MANAGE_EXTERNAL_STORAGE permission, etc.)
Activated our inactive tracks (Open, Closed Alpha, and Beta Testing Tracks), uploaded the same build 2.24.1 (build 1) to these tracks, and then paused those tracks. (I've paused them as I won't use them actively, you may not want to pause it)
Created another build 2.24.1 (build 2) which was completely the same as build 1. I've just updated its build number.
Uploaded 2.24.1 (build 2) to the Internal Testing Track.
Created another build 2.24.1 (build 3) which was completely the same as build 3. I've just updated its build number.
Uploaded 2.24.1 (build 3) to the Production Track.
Went to "Publishing Overview" page, activated Managed Publishing in order to manually publish my uploads to Production and other tracks as they got accepted.
Sent these uploads to review at once and voila, Google accepts your uploads!
Sarcasm on.
Hereby, I would like to congratulate Google Play Support as they've shared all these details within their documentation, within their rejection e-mails, and within their super fast response to the appeal.
Sarcasm off.
I've found this solution referencing from this answer https://stackoverflow.com/a/69933431/2833718. I couldn't find any help from Google's official docs. They've always rejected my uploads with the same e-mail which is impossible to decode for a human being. They've never returned to my appeal.
This migration and support process was completely a failure.
Thank you Google Play Support, you are everything but support to developers.
My Android rejected build is approved finally after 3 weeks of headache.
Basically, Google was checking old APK, if it is available in any of the track (Internal, Open, Closed or Production) with Policy Violation.
So, in this regard you have to roll out the app to 100% in the track which has this Policy violation. Which will deactivate the old build.
I wasn't rolling out the new app to 100%.
Thanks to Google Policy Team.
I Found a solution for my issue .
Actually there was another channel in google play "Internal Testing channel" That has a build with permissions . You need to remove/Update any builds inside any channels to be empty from any Sensitive/ Highly risk permission.
One method for solve your problem, is start one new app. But when you for config your app, put disable the iten that say about file sms and file critical.
Resume, your app is been reject because the uour pre config. And not by your code.
I am on a windows 10 machine and trying to use the Shopify App CLI to create apps, but I am running into some errors.
First I installed ruby so I could use the gem command to install the Shopify App CLI, as explained here.
When running shopify version as explained in the above documentation, I get the following output:
bash: shopify: command not found
After googling for a bit I found a solution to this problem, by running shopify.bat version. With this command I can use the CLI.
Moving on, I tried following this tutorial to create my first Shopify App. I used shopify.bat create node to create my app, moved into the folder and ran shopify.bat serve to serve my app locally.
Now the following problem arises:
It starts promising by installing ngrok:
But after waiting for a bit, I get the following output (Sorry for the screenshot, I could not get it to look normal with inline code):
What I also notice is that it uses C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/shopify-cli-1.4.0/ as the path to the CLI, but when looking on Google, most people have /home/[USER]/.shopify-app-cli/ as the path to the CLI. This path does not exist on my machine.
So I would like to know why first of all the serving of the app won't work, because ngrok can't be found, and second why ~/home/user/.shopify-app-cli does not exist.
Thanks in advance,
Mike
I think modern Windows come with Linux now. Since the Internet runs on Linux, you might find development and following tutorials much easier if you use Linux, since all these inconveniences of Windows disappear. Unless you are already super handy with all the quirks of Windows to work around their results, it could be your ticket!
That being said, I mastered this development pattern using *nix and it remains pretty advanced to actually have a smooth workflow for both localhost and production development. Ngrok itself is painful without paying for the service and using puma-dev and puma-ngrok... I laugh when I think about how those essentials running under Windows will be for you.
This is for anyone else who, like me, is mourning the sad, soon-coming death of Google Play (Music) and annoyed w/the forced moved to YouTube Music. The question/goal I had was simply "how do I move from Google Play (Music) to Plex Music?" so I figured I'd share my notes/steps here in case anyone else finds it helpful. Reminder: Once Google Play is turned off officially (date unknown, end of 2020?) you won't be able to perform some or all of these steps anymore.
1) Download Your Music from Google
Use Google's "Music Manager" app to download your entire library to your hard drive somewhere.
While you can download your music from Google Play using the Chrome "Google Play" extension I don't recommend if you can avoid it because it's buggy and it doesn't make Artist and Album folders for you like the "Music Manager" app does which, IMHO, is helpful vs a folder w/thousands of unorganized MP3 files.
(1B) Some people may need to refer to the pycryptodomex docs if they encounter compiler issues with gmusicapi and plexapi. Thanks to Paul for the heads up.
2) Setup Plex Music Library
Assuming you have a Plex server setup and running, create a "Plex Music" library item and pick the folder(s) it should use. Once this is done, copy all your music from step #1 above to it, tell Plex to scan the folders and wait for it to finish scanning everything. Confirm all your albums/artists show up, in general, as they did in Google Play (Music).
3) Pull Google Play (Music) Playlists into Plex Music
Reference: https://www.reddit.com/r/PleX/comments/hfgnvk/import_google_play_music_playlists/
Install python for Windows (if not installed already)
Run this in a command prompt to install the python script dependencies:
python -m pip install --upgrade pip gmusicapi plexapi requests
Download copy of this python script here
Get these 3 things from your Plex server:
Plex URL (e.g. http://10.10.1.10:32400)
Active Plex Token via these instructions
Name of the Plex Music library you're importing your Google playlists to
Add the 3 Plex items from #4 above to the top of your copy of the python script and save the file.
Run your copy of the python script in a command prompt: python gmusic_playlists_to_plex.py
Follow prompt instructions to authenticate on Google and watch the magic happen
(You may have to run it a second time after authenticating if it throws an error on first try)
Note: A few of my playlists were mangled a bit (maybe due to deleted songs or metadata oddities but fortunately most of my most-recent/most-used playlists copied over fine.
4) Enjoy Plex Music!
While I know maintaining a music locally (via Plex) will require hard drive/backup maintenance work over time, I have to say I am loving Plex Music so far. There seems to be a bug w/the offline sync (w/the iOS app) but I'm sure they'll fix and aside from that the entire library/playlist/queue experience in Plex Music is actually faster and better than Google Play (IMHO) - loving it so far. I also just discovered today that they have a cool new iOS app dedicated entirely to the music stuff that seems even better than the Google Play iOS app: Plexamp.
Thanks again to the Reddit guys for elements in #3. LMK if I left anything important out or should add a step.
The app was build and it was on internal test mode for about 1 month after it was reviewed. I created a production release skipping the alpha and beta test because it was ready to be launch.
After the production release was created, I saw a message saying that the app is being reviewed on the dashboard on Google Play Console. After it was reviewed, it was published but it was label as Internal Beta and I can't find it on the Play Store while searching or it. The version of the app is the old one on the Internal Test. There is no information about what is the problem and how to get the app to publish.
Try to access directly - https://play.google.com/store/apps/details?id=YOURPACKAGENAME
If you are able to access the right version - Great. It's not appearing in search, my be you need to work on marketing.
If you are able to access old version - wait for some time, it's being updated. Sometimes it may take upto 7 days.
If you are unable to access, your app is removed. You should appeal to Google.