AOT runtime error with AWS Amplify and Angular 7 - API is not defined












2














I have set up AWS Amplify in an Angular 7 project using the API module for GraphQL capabilities.



All seems to work when served using ng serve.



If however if I use AOT compilation - e.g. For a production build then I receive no compilation errors but on runtime I see the following error




ERROR Error: Uncaught (in promise): ReferenceError: API is not defined




I have isolated the problem in that AOT is the trigger for it occurring but unsure whether it is an Amplify issue or something silly I am doing regarding Angular.



What am I doing wrong and how can I resolve it?










share|improve this question





























    2














    I have set up AWS Amplify in an Angular 7 project using the API module for GraphQL capabilities.



    All seems to work when served using ng serve.



    If however if I use AOT compilation - e.g. For a production build then I receive no compilation errors but on runtime I see the following error




    ERROR Error: Uncaught (in promise): ReferenceError: API is not defined




    I have isolated the problem in that AOT is the trigger for it occurring but unsure whether it is an Amplify issue or something silly I am doing regarding Angular.



    What am I doing wrong and how can I resolve it?










    share|improve this question



























      2












      2








      2







      I have set up AWS Amplify in an Angular 7 project using the API module for GraphQL capabilities.



      All seems to work when served using ng serve.



      If however if I use AOT compilation - e.g. For a production build then I receive no compilation errors but on runtime I see the following error




      ERROR Error: Uncaught (in promise): ReferenceError: API is not defined




      I have isolated the problem in that AOT is the trigger for it occurring but unsure whether it is an Amplify issue or something silly I am doing regarding Angular.



      What am I doing wrong and how can I resolve it?










      share|improve this question















      I have set up AWS Amplify in an Angular 7 project using the API module for GraphQL capabilities.



      All seems to work when served using ng serve.



      If however if I use AOT compilation - e.g. For a production build then I receive no compilation errors but on runtime I see the following error




      ERROR Error: Uncaught (in promise): ReferenceError: API is not defined




      I have isolated the problem in that AOT is the trigger for it occurring but unsure whether it is an Amplify issue or something silly I am doing regarding Angular.



      What am I doing wrong and how can I resolve it?







      angular angular7 aws-amplify angular-aot






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 26 '18 at 22:39









      nyedidikeke

      2,67441933




      2,67441933










      asked Nov 16 '18 at 15:36









      IThoughtItWouldBeEasy

      161




      161
























          1 Answer
          1






          active

          oldest

          votes


















          0














          For anyone else with this issue try prefixing API with Amplify.API. Not sure why it worked with JIT but not AOT but it solved the problem for me.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53341001%2faot-runtime-error-with-aws-amplify-and-angular-7-api-is-not-defined%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            For anyone else with this issue try prefixing API with Amplify.API. Not sure why it worked with JIT but not AOT but it solved the problem for me.






            share|improve this answer


























              0














              For anyone else with this issue try prefixing API with Amplify.API. Not sure why it worked with JIT but not AOT but it solved the problem for me.






              share|improve this answer
























                0












                0








                0






                For anyone else with this issue try prefixing API with Amplify.API. Not sure why it worked with JIT but not AOT but it solved the problem for me.






                share|improve this answer












                For anyone else with this issue try prefixing API with Amplify.API. Not sure why it worked with JIT but not AOT but it solved the problem for me.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 21 '18 at 21:36









                IThoughtItWouldBeEasy

                161




                161






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53341001%2faot-runtime-error-with-aws-amplify-and-angular-7-api-is-not-defined%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to change which sound is reproduced for terminal bell?

                    Can I use Tabulator js library in my java Spring + Thymeleaf project?

                    Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents