This repository was archived by the owner on Jul 14, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 24
Troubleshooting common problems
jwest-apigee edited this page Sep 6, 2014
·
17 revisions
-
A possible source of error is using incorrect or expired app keys in your configuration. Make sure, for example, that your Twitter credentials are current.
-
If your app needs to parse a request body, be sure to place the bodyParser() before including the Apigee 127 middleware. Here is the recommended pattern:
var a127 = require('a127-magic');
var express = require('express');
var app = express();
app.use(express.bodyParser()); // Call this before including the a127.middleware()
app.use(a127.middleware());
app.listen(process.env.PORT || 10010);
Having Trouble? Try posting your question to the Apigee Community. Or, for more links and resources, check out our Help Page
Need help? Visit the Apigee Community ! |
---|
-
Getting started
-
Add policies to your API
-
Add security policies
-
Deploy your projects
-
Programmatic hooks
-
Good to know about
-
Deep dives
-
Reference topics
-
Troubleshooting and getting help
-
Related resources