Skip to content
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

Unable to build my flutter app after package updation #5800

Open
3 of 14 tasks
poojakansal opened this issue Jan 13, 2025 · 7 comments
Open
3 of 14 tasks

Unable to build my flutter app after package updation #5800

poojakansal opened this issue Jan 13, 2025 · 7 comments
Assignees
Labels
bug Something is not working; the issue has reproducible steps and has been reproduced dependencies Pull requests that update a dependency file

Comments

@poojakansal
Copy link

Description

Last year, I implemented AWS into my application, and everything was working fine. However, after updating the packages, I encountered several issues.
The first issue was related to Drift, as it conflicted with other packages. To resolve this, I override the dependency, but that led to additional issues.
Currently, I’m trying to access the existing AWS storage to retrieve and play audio files, but I’m running into challenges.

final storagePlugin = AmplifyStorageS3();

Usage of AmplifyStorageS3 throwing many errors which I mentioned below

AppData/Local/Pub/Cache/hosted/pub.dev/amplify_storage_s3_dart-0.4.7/lib/src/storage_s3_service/transfer/database/tables.drift.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named '$state'.
i0.ColumnOrderings get createdAt => $state.composableBuilder(
^^^^^^
AppData/Local/Pub/Cache/hosted/pub.dev/amplify_storage_s3_dart-0.4.7/lib/src/storage_s3_service/transfer/database/tables.drift.dart:384:15: Error: The getter '$state' isn't defined for the class '$$TransferRecordsTableOrderingComposer'.

  • '$$TransferRecordsTableOrderingComposer' is from 'package:amplify_storage_s3_dart/src/storage_s3_service/transfer/database/tables.drift.dart'

pubspec.yaml

dependencies:
amplify_flutter: 2.5.0
amplify_auth_cognito: 2.5.0
amplify_storage_s3: ^2.5.0
drift: ^2.18.0
dependency_overrides:
drift: ^2.20.2

Categories

  • Analytics
  • API (REST)
  • API (GraphQL)
  • Auth
  • Authenticator
  • DataStore
  • Notifications (Push)
  • Storage

Steps to Reproduce

dependencies:
amplify_flutter: 2.5.0
amplify_auth_cognito: 2.5.0
amplify_storage_s3: ^2.5.0
drift: ^2.18.0
dependency_overrides:
drift: ^2.20.2

final storagePlugin = AmplifyStorageS3();

Screenshots

Screenshot_1

Platforms

  • iOS
  • Android
  • Web
  • macOS
  • Windows
  • Linux

Flutter Version

3.28.0-2.0.pre.38691

Amplify Flutter Version

2.5.0

Deployment Method

Amplify Gen 2

Schema

No response

@github-actions github-actions bot added pending-triage This issue is in the backlog of issues to triage pending-maintainer-response Pending response from a maintainer of this repository labels Jan 13, 2025
@ekjotmultani
Copy link
Member

Hi @poojakansal , thank you for taking the time to raise this issue and I'm sorry you are facing it. We are currently working on updating our drift dependency which may resolve this issue, I will update you when that is in

@ekjotmultani ekjotmultani self-assigned this Jan 14, 2025
@github-actions github-actions bot removed the pending-maintainer-response Pending response from a maintainer of this repository label Jan 14, 2025
@poojakansal
Copy link
Author

Thank you for your response! Could you please suggest a workaround or an alternative solution to implement the storage functionality? I need to address this urgently as the app is being prepared for Play Store submission.

@github-actions github-actions bot added the pending-maintainer-response Pending response from a maintainer of this repository label Jan 16, 2025
@ekjotmultani
Copy link
Member

Hi @poojakansal , I will attempt to reproduce the given configuration and get back to you with a possible solution

@ekjotmultani ekjotmultani added the to-be-reproduced Issues that have not been reproduced yet, but have reproduction steps provided label Jan 17, 2025
@github-actions github-actions bot removed the pending-maintainer-response Pending response from a maintainer of this repository label Jan 17, 2025
@ekjotmultani ekjotmultani added the dependencies Pull requests that update a dependency file label Jan 17, 2025
@sushil7271
Copy link

Hello, @poojakansal I facing same issue. Did you found any workaround ?

@github-actions github-actions bot added the pending-maintainer-response Pending response from a maintainer of this repository label Jan 17, 2025
@poojakansal
Copy link
Author

Hello, @poojakansal I facing same issue. Did you found any workaround ?

Yes I am able to run code by overriding web package rather than drift. Actually I am using firebase as well, so the major confliction was web version.
My solution is :

dependencies:
web: ^0.5.0

dependency_overrides:
web: ^1.0.0

@ekjotmultani
Copy link
Member

Interesting, so you kept drift the same as what comes with our most recent release?

@github-actions github-actions bot removed the pending-maintainer-response Pending response from a maintainer of this repository label Jan 21, 2025
@poojakansal
Copy link
Author

poojakansal commented Jan 21, 2025 via email

@github-actions github-actions bot added the pending-maintainer-response Pending response from a maintainer of this repository label Jan 21, 2025
@ekjotmultani ekjotmultani added bug Something is not working; the issue has reproducible steps and has been reproduced and removed pending-maintainer-response Pending response from a maintainer of this repository pending-triage This issue is in the backlog of issues to triage to-be-reproduced Issues that have not been reproduced yet, but have reproduction steps provided labels Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working; the issue has reproducible steps and has been reproduced dependencies Pull requests that update a dependency file
Projects
None yet
Development

No branches or pull requests

3 participants