flutter pub deps | grep flutter_soundDescribe the bug
(This is very important. Most of the time we cannot do anything if we do not have information on your bug)
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:checkDevDebugAarMetadata'.
Could not resolve all files for configuration ':app:devDebugRuntimeClasspath'.
Could not resolve xyz.canardoux:tau_sound_core:6.4.8+2.
Required by:
project :app > project :flutter_sound
Could not resolve xyz.canardoux:tau_sound_core:6.4.8+2.
Could not get resource 'https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/6.4.8+2/tau_sound_core-6.4.8+2.pom'.
Could not GET 'https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/6.4.8+2/tau_sound_core-6.4.8+2.pom'. Received status code 403 from server: Forbidden
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
BUILD FAILED in 58s
Exception: Gradle task assembleDevDebug failed with exit code 1


Hi @ibadanisNow ,
Your Problem Report is interesting.
Could not resolve xyz.canardoux:tau_sound_core:6.4.8+2.
tau_sound_core was the name of the Tau Engine until last version, and I renamed it "tau_core".
When I do a new release I do many test before doing it, but unfortunately I do not really test the LITE flavor.
I probably did something wrong with Flutter Sound LITE in 6.4.8
I am going to fix that, now. During the meaning time, you can use temporarily a previous version, until I fix that.
Sorry for that.
EDIT:
Sorry, I am mixing everything. You are using 6.4.8 which is an old version.
Unfortunately I do not have enough resources to maintain this old version.
Sorry, I am mixing everything. You are using 6.4.8 which is an old version.
Unfortunately I do not have enough resources to maintain this old version.
The lack of developers on Flutter Sound is a big problem. Even the Version 8.1.0 is not correctly maintained.
Flutter Sound needs at least one or two developers. Now there are not any. I am working now on another project and Flutter Sound is naked. Big problem for the Flutter Sound users.
Hi,
I also about to post my problem, I also experience this problem but in different version.
` > Could not resolve xyz.canardoux:tau_sound_core:7.7.0+1.
Required by:
project :flutter_sound
Could not resolve xyz.canardoux:tau_sound_core:7.7.0+1.
Could not get resource 'https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.7.0+1/tau_sound_core-7.7.0+1.pom'.
Could not GET 'https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.7.0+1/tau_sound_core-7.7.0+1.pom'. Received status code 403 from server: Forbidden`
Flutter Sound needs 1 or 2 developers. This project has a pretty good health, now, but every projects need to be maintained to stay alive.
Without any developers, Flutter Sound future will not be very easy.
It seems JFrog guys have changed their minds:
https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
UPDATE 4/27/2021: We listened to the community and will keep JCenter as a read-only repository indefinitely. Our customers and the community can continue to rely on JCenter as a reliable mirror for Java packages.
The problem we are facing right now is that we can't use the last "flutter_sounds" version because our app still doesn't support nullability.
My question is: why the old deployed builds are gone from Bintray? Did you delete your account there? Is it possible to reactivate it? Or maybe deploy the old builds on JitPack as well?
If some of you are also stuck on the 6.4.8+2 build, feel free to use this repo:
flutter_sound:
git:
url: https://github.com/Bliq-Open-Source/flutter_sound.git
No, I did not do anything with our bintray/jfrog account.
Probably everything published until last version is still on Bintray.
I have not closed the account.
The last Flutter Sound version is NullSafety compliant. I know that this can be a big problem for the users.
In fact, Dart did a terrible mess with this new feature that is incompatible with previous versions.
The big problem, is actually that Flutter Sound needs one or two developers working on the maintenance.
I do not work anymore on Flutter Sound, because another project is waiting for me.
Without any developers, the Flutter Sound future will be hard. And of course it is not possible to maintain two versions, one with NullSafety feature, and the other without it.
I'm experiencing the same issue:
https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.5.1+2/tau_sound_core-7.5.1+2.pom is returning 403 Forbidden!
* What went wrong:
Could not determine the dependencies of task ':flutter_sound_lite:compileReleaseAidl'.
> Could not resolve all task dependencies for configuration ':flutter_sound_lite:releaseCompileClasspath'.
> Could not resolve xyz.canardoux:tau_sound_core:7.5.1+2.
Required by:
project :flutter_sound_lite
> Could not resolve xyz.canardoux:tau_sound_core:7.5.1+2.
> Could not get resource 'https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.5.1+2/tau_sound_core-7.5.1+2.pom'.
> Could not GET 'https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.5.1+2/tau_sound_core-7.5.1+2.pom'. Received status code 403 from server: Forbidden
On this blog post JFrog announced that they would be sunsetting Bintray, GoCenter, and ChartCenter on May 1st, so it's been 5 days since files hosted on bintray aren't available:

On the post they mention that users should migrate to:
[...] the respective canonical repository, and we will continue to offer both free and paid JFrog Platform cloud subscriptions that can serve other binary distribution needs.
@Larpoux you mentioned that you didn't do anything with your account:
No, I did not do anything with our bintray/jfrog account.
Probably everything published until last version is still on Bintray.
I have not closed the account.
DId you manage to migrate your plan? There's a migration guide on JFrog, I think you fit the free plan, since this package is open source ๐ค.
I saw that you commented on another issue https://github.com/Canardoux/tau/issues/658#issuecomment-821867335 that the Flutter Sound 8.1.1 release is on JitPack. Unofortunatelly I'm unnable to migrate my app to null safety, since a few packages haven't migrated yet.
I don't mean to rush you or anything, just to be clear ๐ . And I thank you for your work!
Also, I can still generate the apk locally, because I still have the package cached, the error above was on our CI. I was just wondering if it is possible to publish a version without null safety to JitPack or on JFrog bintray?
If your App cannot be Null Safety compliant You must use Flutter Sound 7.x .
But :
Of course it should be easy to publish 7.x on JitPack, but Flutter Sound has a big resource problem (no developer), and we are focused on 8.x.
Last point : because 7.x is not maintained, there is no major reason to publish it on JitPack (Jfrog/Bintray probably continues to publish those old releases)
I understand, and I'm trying to use 7.x, but I cannot download any of these old releases.
I've tried with the 5 latest versions from 7.x, but I keep getting 403 status code from bintray server, example with curl:
โ ~ curl -I https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.7.0+1/tau_sound_core-7.7.0+1.pom
HTTP/1.1 403 Forbidden
Server: nginx
Date: Thu, 06 May 2021 17:06:33 GMT
Content-Type: text/plain
Content-Length: 10
Connection: keep-alive
ETag: "578ccc8e-a"
โ ~ curl -I https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.6.7+1/tau_sound_core-7.6.7+1.pom
HTTP/1.1 403 Forbidden
Server: nginx
Date: Thu, 06 May 2021 17:08:37 GMT
Content-Type: text/plain
Content-Length: 10
Connection: keep-alive
ETag: "5c362be6-a"
โ ~ curl -I https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.6.6+1/tau_sound_core-7.6.6+1.pom
HTTP/1.1 403 Forbidden
Server: nginx
Date: Thu, 06 May 2021 17:09:39 GMT
Content-Type: text/plain
Content-Length: 10
Connection: keep-alive
ETag: "578ccc8e-a"
โ ~ curl -I https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.6.5+1/tau_sound_core-7.6.5+1.pom
HTTP/1.1 403 Forbidden
Server: nginx
Date: Thu, 06 May 2021 17:09:49 GMT
Content-Type: text/plain
Content-Length: 10
Connection: keep-alive
ETag: "5c3b2e0f-a"
โ ~ curl -I https://dl.bintray.com/larpoux/TauRepo/xyz/canardoux/tau_sound_core/7.6.4+3/tau_sound_core-7.6.4+3.pom
HTTP/1.1 403 Forbidden
Server: nginx
Date: Thu, 06 May 2021 17:11:23 GMT
Content-Type: text/plain
Content-Length: 10
Connection: keep-alive
ETag: "5c3b2e0c-a"
As you can see, every request returns 403 status code header. So there's no way to build an apk in those versions.
From what I understood from JFrog blog post, they shut down bintray on May 1st, so all requests to bintray won't work.
I understand that 7.x is not maintained, you are focusing on 8.x and that you are short on developers to help. But if it is easy to publish 7.x on JitPack, I would really appreciate it if you could, and I'm sure it would benefit every flutter_sound user that can't upgrade to null safety at the moment
OK, @haga-
Thank you for your investigations. This is a problem. We probably need to publish 7.x on JitPack. This is necessary for Flutter Sound users who are not ready to use the Null Safety compliance.
This is not very difficult, but the only developer who can efficiently do that is me. :-(
And actually I do not work on Flutter Sound.
I am afraid that I have to go back on Flutter Sound to solve that.
I will tell you if I can get some free time for this task.
Oh, I thought you did ๐ .
Glad I could help somehow ๐ .
Great, thank you, @Larpoux!
@haga- If you have the dependency cached on your machine, you can do the same we did here:
https://github.com/Canardoux/tau/issues/671#issuecomment-832591594
flutter_sound folder from the plugin's folder (inside the "~/.pub-cache") and create your own git repository with that codeimplementation files('libs/tau_sound_core-7.6.7+1.aar')
Use your that repo in your pubspec.yaml file.
Share your git repository's url with other here. :)
Thank you very much @duduBaiao for sharing a turn around solution.
Any way, I will work on publishing 7.x on JitPack at the end of the week or beginning of next week.
OK, Guys and Girls,
Can you check if 7.8.0 is OK both on Android and iOS ?
This version is supposed to be published on JitPack and is not Null Safety compliant.
7.8.0 Not working :( @Larpoux
??? This kind of post has strictely no value.
Hi @Larpoux , Goodday.
I really appreciate your work on the flutter_sound plugin and for also taking the time to publish the v7 to Jitpack.
After changing the flutter_sound plugin to 7.8.0, I tried running on an Android device but it doesn't work on Android.
Error logs below:
Build file '/Users/User/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_sound-7.8.0/android/build.gradle' line: 61
* What went wrong:
A problem occurred evaluating project ':flutter_sound'.
> Project with path ':tau_sound_core' could not be found in project ':flutter_sound'.
Thebuild.gradle file:
````
ext.flutterFFmpegPackage = 'audio'
group 'com.dooboolab.fluttersound'
version '7.8.0'
buildscript {
repositories {
google()
mavenCentral()
maven { url "https://dl.bintray.com/larpoux/TauRepo" }
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:4.1.1'
}
}
rootProject.allprojects {
repositories {
google()
mavenCentral()
maven { url "https://dl.bintray.com/larpoux/TauRepo" }
jcenter()
}
}
apply plugin: 'com.android.library'
android {
compileSdkVersion 30
defaultConfig {
minSdkVersion 18 // 18 works fine for the player, but the recorder needs at least 24
}
lintOptions {
disable 'InvalidPackage'
}
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
}
String safeExtGet(String prop, String fallback) {
rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
}
//ext.flutterFFmpegPackage = 'full-lts'
dependencies {
implementation 'com.arthenica:mobile-ffmpeg-full:4.4.LTS'
implementation 'androidx.core:core:1.3.2'
implementation 'androidx.media:media:1.2.0'
implementation 'androidx.appcompat:appcompat:1.2.0'
// -------------------------------------------------------------------------------------
// CAUTION: The following instruction is for developping and debugging the Flauto Engine
// DO NOT INCLUDE THE FOLLOWING LINE IN A REAL APP !!!
implementation project(':tau_sound_core')
//implementation 'xyz.canardoux:tau_sound_core:7.7.0+1'
// -------------------------------------------------------------------------------------
}
Hi @Larpoux - I echo everyone's appreciation for your support by publishing 7.8.0 on Jitpack.
I have updated the maven field to:
rootProject.allprojects {
repositories {
google()
mavenCentral()
maven { url 'https://jitpack.io' }
jcenter()
}
}
and the dependency injection to:
```
dependencies {
implementation 'com.arthenica:mobile-ffmpeg-full:4.4.LTS'
implementation 'androidx.core:core:1.3.2'
implementation 'androidx.media:media:1.2.0'
implementation 'androidx.appcompat:appcompat:1.2.0'
// -------------------------------------------------------------------------------------
// CAUTION: The following instruction is for developping and debugging the Flauto Engine
// DO NOT INCLUDE THE FOLLOWING LINE IN A REAL APP !!!
// implementation project(':tau_sound_core')
// implementation 'xyz.canardoux:tau_sound_core:7.7.0+1'
implementation 'com.github.Canardoux:tau:7.8.0'
// -------------------------------------------------------------------------------------
}
Yet I am still getting a build failure error, since the repository on Jitpack seems to require some sort of authentication:
FAILURE: Build failed with an exception.
Would greatly appreciate your help on how to proceed!
Hello, every body.
I just fixed several things on 7.x .
Please could you check if 7.8.4 is better, now ?
Thanks
Hello @Larpoux,
I can confirm the version 7.8.4 works fine and builds without errors.
Thanks once again for your time and contributions to the Open Source community!
Most helpful comment
https://jitpack.io/#Canardoux/tau_core