-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PWA Builder]: Support for Android SDK 34 #4766
Comments
Why put a start date of Aug 31, 2024 if they're going to start enforcing it sooner 😭 hopefully this gets fixed soon enough. My guess is it isn't an issue on PWABuilder's side, rather on Bubblewrap's side |
@jere-mie Yes, remarkable, I noticed that too. Maybe the different teams within Google are not aligned. |
Same here |
Been having this for a few days also |
Please use the thumbs up on the original issue, don't "same here" the thumbs up will bring attention better and leave the issue readable down the line - thank you :) |
In the meantime you can work around this by changing the
|
^ There is also another easy workaround if you can use Android Studio, you can select to include Source code while generating the Android package on PWABuilder, so you can open the project and update the compilesdk/targetsdk, and build/sign again. |
Hello all! Sorry for the delay, I was on holiday for July 4th here in the US. I am working with our team to get Bubblewrap + PWABuilder updated and will post here when things are updated. Both @Twey and @maiconcarraro 's workarounds are great. Using Android Studio is what I would recommend for now if you are blocked. |
And this is the issue to get Bubblewrap updated GoogleChromeLabs/bubblewrap#860 |
@jgw96 and @maiconcarraro After changing the compile and target SDK in the build.gradle file, some warnings are shown when compiling the project. |
@jonkerw85 |
@kiajiko Thanks for the support. Upgrading the Gradle version indeed resolves the warnings. |
Just fyi, there's another update needed for PWA's that enable Play Billing. I believe the android-browser-helper billing library version that PWABuilder points to would need to be updated (after the library itself is updated to support Play Billing 7.0), see also GoogleChrome/android-browser-helper#473 |
Hi @jgw96 waiting for your update about [SDK 34] |
If Google are going to do things like this, it would be useful if PWA Builder included a field where we could override defaults, maybe an optional field that could show json for the defaults which would then let you override them if you want. |
Hi @jgw96 We are waiting for updates about [SDK 34] |
Any chance you can do a quick youtube guide on how to do this? I'm new to Android studio and worried about the deadline. Your help is much appreciated |
Why it takes so long to solve the problem on PWA Builder with SDK 34 is not a serious approach to users who trust you. |
@Zimasl pwabuilder is built on top of bubblewrap, and that's where the update needs to be made. It isn't something pwabuilder can immediately fix. Several users have mentioned alternative solutions you can try out in the meantime |
let me know if you need something different: https://youtu.be/DbarW15E058 |
i get error after click on "upgrade to grandle 8.5 and re-sync":
and i dont see "change grande version ... and re-import project" what to do? |
@Aviv1000 I had the same issue. Make sure to update the gradle version as shown in step 8 in the video to 8.5.1. You'll have to edit the file |
sorry for missing this, maybe because I already did earlier it skipped a step, happy that you managed to figure out. |
@arladmin you should move your comment to bubblewrapper repo, the point of PWABuilder is still the same, and they are not asking manual interventions as the final solution... only if you are really blocked and need it asap, people are just sharing workarounds until it is fixed, you can do manual interventions if you want to fix before the Google team on bubblewrapper repo. your comment is the kind of fiasco that ruins opensource communities, if you can't understand how dependencies work you can't blame others for your lacking of knowledge. peace. |
Hello all! The PR for Bubblewrap, which is the dependency that needed to be updated first, has been merged! We are now one step closer to having this updated in PWABuilder itself. I apologize for those having to use the workaround for now, but I much appreciate the patience as this is not a one-and-done kind of update. We plan to have PWABuilder updated long before the end of August deadline. |
Hi @jgw96 , |
Hello @iAmKabiru, from what I've seen and read we are now waiting for a new release of Bubblewrap now that the PR has been merged. I haven't found any release schedule on behalf of Bubblewrap. |
Hello @jgw96 Is there any update on this? MT |
Hi all! As you can see in the linked issue on the Bubblewrap repo, we are waiting for them to release the latest version. We are very well aware of the schedule here, as is the Bubblewrap team. Just like everyone here, we would love to already have this update out, but that is simply not possible in a manageable way unfortunately. Please know that I am keeping a close eye on this and will update everyone as soon as the update has happened. Thanks everyone! |
Hi, I have the same problem. My application is pwa and I think the person who generates this pac is the PWA Builder itself. Do we have any plans to update? error "App needs to target Android 14 (API level 34) or newer" |
Boa tarde! Alguma novidade sobre a versão SDK34 no PWA Builder? |
@leeobrum this comment #4766 (comment) has the current status, thanks! |
Can this be added as a note on PWABuilder.com site so that everyone using will be aware of this issue. |
+1 |
Hi, I have the same problem. any updates? |
BubbleWrap just released a new version with support for sdk 35. |
Hello all! I am finally kicking off work to update our service. We have been waiting on the Bubblewrap team to do a release and as @catalescu put above, they published an updated version. I am starting on this today and hope to have it out asap. The latest would be the end of next week. |
Hello all! I have things working in the PR linked above. It is late today where I am and my team does not deploy on Fridays, so I will do last testing, merge and then publish to production on Monday (the 12th) |
@jgw96 Something went wrong |
lilpwa mentioned in discord that was pushed from codespace to get around a Github actions issue, you can confirm the last version is deployed because the new signed key is working + txt file contains same password (workaround for now) they are probably going to investigate/address the issues related to GH action and other things, but you should be good to generate the app already (worked for me) |
Solved for me. Thank you. |
Something is quite wrong, I'm getting this error when I'm trying PWA Builder:
|
Hi, when is this going to be available on https://www.pwabuilder.com ? I made a package recently and the target SDK is still below the required one. I'm not sure where releases to the web version are tracked. Thanks 🙏 |
@angrykoala when did you generate? lilpwa updated the website, if there is still an issue you can open a new issue, or ask help in discord. |
Thanks @maiconcarraro I did it a couple of days ago, I'll try again today |
It works for me, but the Playstore review process takes a long time. (3-5 days) |
Today, I downloaded the source files for an Android application from pwabuilder.com, and the target sdk is set to 35. @angrykoala |
Just to +1 this is correct and I was also able to publish via pwabuilder.com last week. sdk of my app is now v35 and has been published to google play without issue. |
Tell us about your feature idea
Google again changed the API level requirements.
App must target Android 14 (API level 34) or higher starting from Aug 31, 2024
Current supported version is 33
bubblewrap does not seem to be updated so far, too.
Do you have an implementation or a solution in mind?
Download source code from pwabuilder.com and compile with new version.
Have you considered any alternatives?
No response
The text was updated successfully, but these errors were encountered: