-
Notifications
You must be signed in to change notification settings - Fork 199
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
Build Old AWS Project #2872
Labels
question
General question
Comments
@smediomike Thanks for opening the issue.
|
harsh62
added
the
pending-community-response
Issue is pending response from the issue requestor
label
Apr 21, 2023
Hello
please see my below comment:
* Have you tried cleaning and clearing the derived data from the machine?
==> Yes, I tried to clear all issue, folder and derived data
* Would you be able to share the POD file? ==> please see attachement
* If you have done anything different for release builds?
==> no, i used save environment, i re-do according to AWS’s website document based on current project.
* Do you have any special handling been done in the build script phase?
==> no
Finally i resolved this issue at the steps:
1, make new same name xcode project
2, excute pod command like website document to initliaze and create workspace
3, copy old project files to replace new project, keep new workspace and pod project.
4, as this, i can make release build. so this issue should relate with the paths in build script’s release enviorment.
Regards,
mike.wu
在 2023年4月22日 01:14,Harshdeep ***@***.***> 写道:
@smediomike<https://github.com/smediomike> Thanks for opening the issue.
I cannot repro the issue in my local. Setting up with POD seems to work fine at my end. Some questions I have are:
* Have you tried cleaning and clearing the derived data from the machine?
* Would you be able to share the POD file?
* If you have done anything different for release builds?
* Do you have any special handling been done in the build script phase?
—
Reply to this email directly, view it on GitHub<#2872 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADD6F3QMKGC5YF7SQ3YWYPTXCK6AFANCNFSM6AAAAAAXCHQDMY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
github-actions
bot
removed
the
pending-community-response
Issue is pending response from the issue requestor
label
Apr 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have one GM product which already run on market, but my Mac system happen critical issue, I have to move to another new Mac system. but I can not make release build based on whole orginal project source with AWS Pod successfully.
Steps To Reproduce
Expected behavior
It's better one system make correct project, another environment can copy and make build. or can make old project with case #2 steps.
Amplify Framework Version
1.28.1
Amplify Categories
API, DataStore, Storage
Dependency manager
Cocoapods
Swift version
5.0
CLI version
4.4
Xcode version
Xcode 14.2.1
Relevant log output
Is this a regression?
No
Regression additional context
No response
Device
Any
iOS Version
iOS16 etc
Specific to simulators
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: